text:
Building political integrity is the premise of the effective operation of a democratic system. In 2013 the CPC and the Chinese government further intensified their efforts to combat corruption, putting power, government operations and personnel management under institutional checks to ensure that the people oversee the exercise of power and that power is exercised in a transparent manner. Institutional reform of the State Council was fully launched; the central government decentralized and canceled 416 items of administrative approvals in 2013. In view of multiple corruption problems in certain fields, the CPC Central Committee issued the Work Plan for Establishing and Improving the System of Preventing and Punishing Corruption (2013-2017). In 2013 discipline inspection and procuratorial organs at all levels received 1,950,374 complaints of related offences through petition visits and letters, including 1,220,191 accusatory and prosecutable cases; filed 172,532 cases, concluded 173,186 cases, and punished 182,038 violators. In 2013 procuratorial organs at all levels filed and investigated 37,551 cases of official crimes involving 51,306 suspects, up 9.4percent and 8.4percent respectively on a year-on-year basis. China increased its efforts to handle major cases, filed and investigated 2,581 cases of embezzlement, bribery and appropriation of public funds, each involving over 1 million yuan, and 2,871 state functionaries at and above the county/division level, including 253 officials at the prefecture/bureau level and eight at the provincial/ministerial level. The courts at all levels fully performed their duty of combating corruption through criminal trials, intensified efforts to punish embezzlement and bribery crimes, wound up 29,000 cases of embezzlement, bribery, dereliction of duty and infringement of rights by state functionaries, and convicted 31,000 persons.
In China, socialist consultative democracy is an important form of ensuring the people's democratic rights. Socialist consultative democracy values final decision-making results as well as extensive public participation in decision-making, stresses respect for the opinion of the majority as well as ensuring that the minority can fully express their opinion and protect their own rights, thereby expanding the scope of democracy so as to realize the people's democracy to the maximum extent. In 2013 China accelerated the building of a consultative democratic system with reasonable procedures and complete links, expanded the consultation channels of state power organs, Chinese People's Political Consultative Conference (CPPCC) organizations, political parties and groups, community-level and non-governmental organizations, and conducted extensive consultations on issues relating to legislation, administration, democracy, political participation and social problems. Taking these specific consultation forms as the base, China conducted extensive consultations on major issues in social and economic development and specific problems concerning the immediate interests of the people, so as to reach and enhance agreement. As an important channel of consultative democracy, the CPPCC vigorously promotes consultative democracy, innovates consultation forms categorized by specialized topics, connecting all social circles, relying on special committees and by means of panel discussions; actively conducts consultations on particular topics, between representatives from relevant sectors of society, between parties with common concern, and with relevant departments in the handling of proposals. It promotes diversified consultation activities, invites responsible persons of related departments to listen to opinions and proposals directly, so as to transform such opinions and proposals into tangible results. The CPPCC makes specific plans for consultation topics, forms and activity organizations every year. In 2013, it carried on and innovated the biweekly "consultation symposium" mechanism, and conducted consultations on macroeconomy, architectural industrialization, protecting the interests of workers and staff members, deepening the reform of scientific and technological systems, enhancing automobile exhaust control and other topics.
Community-level democracy is being advanced in an orderly manner, and protection of electoral rights and community-level autonomy have been further strengthened. In 2013 the Procedures of the People's Republic of China on the Election of Villagers' Committees was promulgated and implemented, which further specifies the procedures and requirements of villagers' committee elections. Secret ballot and open vote-counting are fully practiced; secret ballot booths have been set up; and campaign speeches and village governance speeches are being extensively promoted. Now, 98percent of villages in China have formulated village regulations, villagers' agreements and rules for self-governance by villagers; villager's participation in decision-making and management of their own affairs has been improved by a large margin. By the end of 2013 cities and towns throughout China had held seven rounds of general elections for community residents' committees. Proprietors' management committees and other non-government and volunteer organizations are now playing a greater role in community democratic self-governance. (more)


text: The Argus wiki last edited by fesak on 05/05/13 10:31AM View full history There are several characters in Greek legend using the name Argus/Argos. The following are the most notable. Argus Panoptes (Argus the All-Seeing)Argus is a giant with a hundred eyes and servant to Hera. His task was to guard a sacred heifer, but this heifer was actually a disguise of Io, a nymph whom Zeus favored. Zeus had plans to mate with Io in order to bring about a new lineage to thwart the Gods. Argus often slept with several eyes open but he failed to prevent Hermes from the spells which he cast, a task Zeus ordered. Hermes was able to slew Argus. Argus, Son of ArestorArgus is often noted for being responsible for the construction of Jason and The Argonauts' ship, Argo.

subset: commoncrawl


text:
Thanks for helping us sort this video!
Thanks for helping us associate the correct Pornstars to this video!
Help Us: Do these Pornstars appear in this video?
Pornstar Name:
All Comments (6)
Melanie is simply amazing. Uber sexy babe !!
you just lock onto her eyes and everything after that is just gravy !
Vaya cuerpo tiene mas hermoso la niña y que ojos mas bonitos tiene
holy crap


text:
|Publication number
|Publication type
|Application number
|Publication date
|Mar 7, 2006
|Filing date
|Apr 21, 2000
|Priority date
|Apr 21, 2000
|Fee status
|Publication number
|Sai V. Allavarpu, Shivaram Bhat
|Original Assignee
|Sun Microsystems, Inc.
|Export Citation
|BiBTeX, EndNote, RefMan
|Patent Citations (49), Non-Patent Citations (22), Referenced by (84), Classifications (18), Legal Events (4)
|External Links: USPTO, USPTO Assignment, Espacenet
1. Field of the Invention
The present invention relates generally to computer software. More particularly, the present invention relates to network management software.
2. Description of the Relevant Art
The field of network management involves the management of networked devices, often remotely. A computer network is a linked group of two or more computers. Generally, networks may be classified as Local-Area Networks (LANs) or Wide-Area Networks (WANs). In a LAN, the computers or devices are typically connected together within a "local" area such as a home, office, or group of offices. In a WAN, the computers or devices are typically separated by a greater distance and are often connected via telephone/communication lines, radio waves, or other suitable means of connection.
Networks are usually classified using three properties: topology, protocol, and architecture. Topology specifies the geometric arrangement of the network. Common topologies are bus, ring, and star configurations. A network's protocol specifies a common set of rules and/or signals, such as Ethernet or Token Ring, which the networked devices use to communicate with each other. A network's architecture typically specifies one of the two major types of network architecture: peer-to-peer or client/server. In a peer-to-peer networking configuration, there is no server, and computers simply connect with each other in a workgroup to share files, printers, services, and Internet access. Client/server networks often include a domain controller to which all of the networked computers log on. This server may provide various services such as centrally routed Internet access, e-mail, file sharing, printer access, and security services.
Many types of devices may be managed over a network, such as printers, scanners, phone systems, copiers, and many other devices and appliances configured for network operation. Typically, such devices are managed via requests and events. A request is a message sent to a managed object. A request may be sent by a manager application to a managed object to query the object about a particular parameter associated with the object. A request may also be sent to a managed object to modify a parameter of the object. Alternately, an event is a message originating with a managed object. Events may be sent by managed objects to signal some change of state of the managed object, or to communicate information about the managed object. Managing such devices tends to require that the data types of each device's control parameters and signals be well defined. For example, a networked printer might have a Boolean status parameter which indicates whether the device is currently on or off and a control parameter which turns the printer on or off. A manager application may send a request to determine the on/off status of the printer. Then, once the status is determined, say, to be off, a subsequent request may be sent to modify the control parameter to turn the printer on. The printer may also be capable of generating an alert signal indicating, for example, that the toner level is low. In this case, an event communicating that fact may be sent by the managed object (the printer) to the appropriate manager application.
The network management software should be able to read and write these data correctly in order to manage the device. To do this, information about the data is required. Such information is referred to as metadata, or "data about data." Metadata may typically describe what type of data (string, integer, Boolean, structure) an object has and how the data are formatted. Metadata is essential for understanding information related to managed devices, as well as information stored in data warehouses. Typically, network management software manages a given device by storing and manipulating a representation of its pertinent data as a software object, herein referred to as a "managed object." This object is the virtual representation of the device on the network.
One TMN approach to managing objects over a network is the Simple Network Management Protocol (SNMP), a set of protocols for managing complex networks. SNMP works by sending messages, called protocol data units (PDUs), to different parts of a network. SNMP-compliant devices, called agents, store data about themselves in Management Information Bases (MIBs) and return this data to the SNMP requesters. The metadata used by SNMP to describe managed object data variables includes the variable title, the data type of the variable (e.g. integer, string), whether the variable is read-only or read-write, and the value of the variable. SNMP works over the TCP/IP (Transport Control Protocol/Internet Protocol) communication stack. SNMP also uses UDP over IP, and also may support TCP over IP. It is widely held, however, that SNMP was developed as a simple "quick fix" and was never intended to be a permanent solution to network management. Consequently, one problem with SNMP is that the information it specifies is neither detailed nor well-organized enough to adequately serve the expanding needs of modern networking.
Another example of a TMN network management protocol is the Common Management Information Protocol (CMIP). In the U.S. the CMIP protocol is primarily run over TCP/IP, while in Europe it is generally run over the OSI (Open Systems Interconnection) communication stack and was designed to replace SNMP and address SNMP's shortcomings by providing a larger, more detailed network manager. Its basic design is similar to SNMP: Management requests, management responses, and notifications are employed to monitor a network. These correspond to SNMP's PDUs. CMIP, however, contains eleven types of messages, compared to SNMP's five types of PDUs.
In CMIP, variables are seen as complex and sophisticated data structures with many attributes. These include: variable attributes, which represent the variable's characteristics (e.g., its data type, whether it is writable); variable behaviors, or the actions of that variable that can be triggered; and notifications, or event reports generated by the variable whenever a specified event occurs (e.g., a terminal shutdown would cause a variable notification event).
As a comparison, SNMP only employs variable attributes and notifications, but not variable behaviors. One of the strongest features of the CMIP protocol is that its variables not only relay information to and from the terminal (as in SNMP), but they can also be used to perform tasks that would be impossible under SNMP. For instance, if a terminal on a network cannot reach its fileserver for a predetermined number of tries, then CMIP can notify the appropriate personnel of the event. With SNMP, a user would need to explicitly keep track of the number of unsuccessful attempts to reach the fileserver. CMIP thus results in a more efficient network management system, as less work is required by a user to keep updated on the status of the network.
A significant disadvantage of the CMIP protocol is that it requires more system resources than SNMP, often by a factor of ten. Thus, any move to CMIP from SNMP requires a dramatic upgrade in network resources. Another disadvantage with CMIP is that it is very difficult to program; the variable metadata includes so many different components that few programmers are generally able to use the variables to their full potential.
Both of the above protocols have been implemented in a number of programming languages, such as C, C++, and Java™. However, network management software which takes advantage of SNMP or CMIP must be written specifically for the language of the protocol implementation. In other words, SNMP-based and CMIP-based network management software is dependent upon a particular programming language and protocol implementation.
GDMO (Guidelines for Definition of Managed Objects) is a standard for defining objects in a network in a consistent way. With a consistent "language" for describing such objects as workstations, LAN servers, and switches, programs can be written to control or sense the status of network elements throughout a network. GDMO prescribes how a network product manufacturer must describe the product formally so that others can write programs that recognize and deal with the product. Using GDMO with ASN1, descriptions may be made of the class or classes of the object, how the object behaves, its attributes, and classes that it may inherit.
GDMO is part of the CMIP and also the guideline for defining network objects under TMN. The object definitions created using GDMO and related tools form a Management Information Base (MIB). GDMO uses Abstract Syntax Notation One (ASN1) as the rules for syntax and attribute encoding when defining the objects. Abstract Syntax Notation One is a language that defines the way data is sent across dissimilar communication systems. ASN1 ensures that the data received is the same as the data transmitted by providing a common syntax for specifying application layer (e.g., program-to-program communications) protocols. Each communications system contains a similar ASN1 encoding/decoding scheme written in the language used on that particular system. When one system wants to send data to another, the first system encodes the data into ASN1, sends the data, and the second system receives and decodes the data using the decoder written in the language used on that system.
In response to the difficulties presented by SNMP and CMIP, the Object Management Group (OMG) and Joint Inter-Domain Management (JIDM) have defined Interface Definition Language (IDL) for network management, which is used to access object instance data and may be used across a plurality of programming languages and across a plurality of platforms. JIDM IDL allows programmers to write only one set of interfaces for a particular object across multiple programming languages, rather than having to write a new set of interfaces for each programming language.
A middleware standard used extensively in network management is the Common Object Request Broker Architecture (CORBA), which is provided by the Object Management Group (OMG). CORBA specifies a system that provides interoperability between objects in a heterogeneous, distributed environment and in a way transparent to the programmer. Its design is based on the OMG Object Model, which defines common object semantics for specifying the externally visible characteristics of objects in a standard and implementation-independent way. In this model, clients request services from objects (which will also be called servers) through a well-defined interface. This interface is specified in the OMG Interface Definition Language (IDL).
In CORBA, a client accesses an object by issuing a request to the object. The request is an event, and it carries information including an operation, the object reference of the service provider, and actual parameters, if any. The object reference is an object name that reliably defines an object.
A central component of CORBA is the Object Request Broker (ORB). The ORB encompasses the communication infrastructure necessary to identify and locate objects, handle connection management, and deliver data. In general, the ORB is not required to be a single component; it is simply defined by its interfaces. The basic functionality provided by the ORB includes passing the requests from clients to the object implementations on which they are invoked. The ORB acts as the middleware between clients and servers. In the CORBA model, a client can request a service without knowing anything about what servers are attached to the network. The various ORBs receive the requests, forward them to the appropriate servers, and then hand the results back to the client.
In CORBA, a client first looks up the object (server) it wants to communicate with. The ORB, as a result of the lookup operation, returns an object reference (a handle) of the server to the client. The client then uses the object reference to invoke operations on the object as a function call in the chosen programming language. The ORB intercepts the client request, collects the information about the operation and the request parameter values, encodes it in IIOP, and sends it to the object (server). The ORB on the object side (server) translates the request into a programming language specific function call on the server object. The server object then processes the request and returns a response, if any. The ORB intercepts the response, encodes the response and its parameters into IIOP, and sends it to the client. The ORB on the client side then returns the response to the client as the return value of the function call originally made as part of issuing the request.
In many cases, CORBA gateways to specific services may be developed to manage specific network traffic, such as requests and events. Typically, these gateways are designed as single-threaded programs. However, increasingly, the benefits of multi-threading are desired for applications and server programs related to network management.
Multi-Threaded Applications
A thread is an encapsulation of the flow of control in a program. Most programs are single-threaded; they only execute one path through their code at a time. Multi-threaded programs may have several threads running through different code paths simultaneously. Multi-threading typically means sharing a single CPU between multiple threads in a way designed to minimize the time required to switch threads. This is accomplished by sharing as much as possible of the program execution environment between the different threads so that very little state needs to be saved and restored when changing threads. Furthermore, if a computer has multiple CPUs and a program has multiple threads, multiple threads of the program may be run on separate CPUs concurrently. Thus multi-threading allows applications to scale with the number of CPUs, as well.
Multi-threading differs from multi-tasking in that threads share more of their environment with each other than do tasks under multi-tasking. Threads may be distinguished only by the value of their program counters and stack pointers while sharing a single address space and set of global variables. Often, there is very little protection of one thread from another, in contrast to multi-tasking. Multi-threading can thus be used for very fine-grained multi-tasking at the level of a few instructions and therefore can hide latency by keeping the processor busy after one thread issues a long-latency instruction on which subsequent instructions in that thread depend.
In a typical process in which multiple threads are used, zero or more threads may actually be running at any one time. This depends on the number of CPUs used by the computer on which the process is running, and also on how the threads system is implemented. A machine with n CPUs may run no more than n threads in parallel, but it may give the appearance of running many more than n threads simultaneously by sharing the CPUs among threads.
A context switch between two threads in a single process is considerably more efficient than a context switch between two processes. In addition, the fact that all data except for stack and registers are shared between threads makes them a natural vehicle for expressing tasks that may be broken down into subtasks that may be run cooperatively. Global variables and resources are shared between threads within the same process. Each thread has its own stack.
In many ways, the use of threads provides benefits over the use of processes in that threads are more efficient to create, switching between threads in the same process is much more efficient than switching processes, and there is easier sharing of resources between threads. Context switching among threads is very efficient in that there are no page or segment table manipulations, no flushing of the associative memory cache (when switching among threads sharing an address space), and no copying of data when exchanging messages among threads of the same address space.
As used herein, "thread-safe" refers to the property that a program may safely use or be used by multiple threads to avoid, for example, data inconsistencies, access collisions, coherency problems, and other errors. When multiple threads share resources, access to the resources should be synchronized to ensure thread-safety. One way this may be accomplished is through the use of a mutual exclusion (mutex) object. A mutual exclusion object allows multiple threads to synchronize access to shared resources. A mutex has two states: locked and unlocked. Once a mutex has been locked by a thread, other threads attempting to lock it will be blocked. When the locking thread unlocks (releases) the mutex, one of the blocked threads may acquire (lock) it and proceed. When managed object events and responses are delivered to a client manager application using multiple threads, synchronization and serialization of the event and response deliveries may become problematic in that the use of different threads to deliver sequential events may introduce chronological inconsistencies due to differing thread execution times. In other words, if a first event is sent using a first thread, and a subsequent second event is sent using a second thread, then depending upon the execution times of the two threads, the second event may actually be delivered prior to the first event.
The existing standards for TMN event management do not address the issue of Access control to TMN events in a platform-independent interface. Currently, that is, mechanisms do not exist to readily manage which TMN manager applications have access to particular managed object events. In addition, clients are required to receive events only indirectly, by creating Common Management Information Service (CMIS) filters. These shortcomings may result in substantial loss of scalability and performance with regard to TMN object event management. Furthermore, the issues of client authentication, object-level access control, and security/audit trails for TMN system usage are not addressed by existing standards. Finally, the existing standards do not allow the clients the option to choose the format in which to receive events.
Therefore, improved systems and methods for managing objects over a network are desired.
The problems outlined above are in large part solved by various embodiments of a system and method for managing object events over a network. A CORBA Gateway between CORBA-based applications and an enterprise manager may be configurable to manage various networked objects, such as printers, scanners, copiers, telephone systems, cell phones, cell phone towers, phone systems, faxes, routers, switches, etc., which may be interconnected via networks. CORBA-based TMN manager applications may be communicatively coupled to a CORBA Object Request Broker (ORB). The manager applications may be operable to send Interface Definition Language (IDL) requests and receive IDL responses and CORBA events through the CORBA ORB. The CORBA Gateway may also be communicatively coupled to the CORBA ORB and be operable to communicate with the CORBA ORB via communications methods such as the Internet Inter-Object Protocol (IIOP), also known as the Internet Inter-ORB Protocol, and IDL. The enterprise manager may be coupled to the CORBA gateway via a proprietary or platform-dependent interface such as Portable Management Interface (PMI) from Sun Microsystems, Inc. The enterprise manager may include a Management Information System (MIS) through which managed objects may be accessed. In one embodiment, the CORBA gateway may translate the enterprise manager PMI events and PMI responses to IDL/IIOP events and responses which may be passed on through the CORBA ORB to the manager applications in the form of IDL responses and CORBA events. Similarly, the CORBA gateway may translate the CORBA manager requests from IDL to PMI requests. Various embodiments of the CORBA Gateway may include one or more components such as an Event Gateway which manages object events and a Request Gateway which manages object requests and responses.
In one embodiment, the CORBA Event Gateway is designed to leverage existing Event Distribution Server (EDS) sinks to provide EDS filtering functionality and EDS object level access control functionality. Therefore, the high-level design philosophy of the Event Gateway is to CORBA-enable EDS sinks. In particular, the approach leverages existing EDS solutions by providing a common sink for all events/notifications and using a unique Event Port Registry to manage the subscriptions of various TMN clients that subscribe for such events/notifications. The approach improves performance and scalability by allowing event sinks to be distributed. Instead of having all clients receive their events from one event sink, the approach allows clients to receive events from different sinks, thereby providing load-balancing. In one embodiment, multiple instances of CORBA-enabled EDS sinks may be running in a single system, thereby allowing different CORBA clients to receive events from different CORBA-enabled EDS sinks. However, CORBA clients are not aware of this multitude of CORBA-enabled EDS sinks because this feature is transparent to the clients.
Generally, the approach described provides the capability to filter events according to criteria presented by client event subscriptions. In one embodiment, the events may be filtered to enforce policy-based access control on TMN events/notifications, determining which CORBA client applications have access to which events. The filtering of events at the sink based upon client subscriptions decreases unnecessary network traffic in that events may be "pushed" to the client, rather than delivered upon client request. This is a substantial improvement over standard polling approaches. In addition, the approach may provide easy-to-use IDL APIs that allow CORBA clients to directly subscribe/unsubscribe to events based on criteria such as object class, object instance, and event type. For example, a print manager application may subscribe to all events relating to the toner supply of laser printers of a particular make and model. The use of IDL may provide a platform-independent interface to deliver events generated by one or more managed objects to manager applications through the Event Gateway. Event subscriptions may be managed with services provided by an event port registry server.
An EventPortRegistry Server, an Event Distribution System (EDS), a Management Information System (MIS), a Request Gateway, and one or more TMN Manager Applications may be communicatively coupled to one another as appropriate, via Internet Inter-Object Protocol (IIOP). The MIS provides an interface through which requests and events may be communicated with managed objects on the network. Events originating with a managed object may be passed by the MIS to the EDS Source, which routes the message to an EDS Sink, where event filtering may occur in accordance with client subscription specifications. The EDS Sink may then determine which clients are to receive the event and route the event to the appropriate ports, which correspond to the subscribing clients. In this manner, events may be filtered at the sink level rather than on the client side, which greatly reduces network traffic.
In one embodiment, an Event Distribution Server (EDS) which is coupled to the event port registry server is configurable to listen for events generated by the one or more managed objects and to deliver the events to the one or more managers, depending upon the managers' event subscriptions and event access control. The EDS may include an EDS Source and one or more EDS Sinks. In one embodiment, a CORBA client may listen for events by creating and registering EventPorts and creating an Event Forwarding Discriminator (EFD). When the create request is processed by the CORBA Request Gateway and sent to the MIS, the EFD may process this create request and send the AE-Title as a listener to one of the EDS Sinks. The EDS code will preferably take care of this automatically.
When the EDS Sink gets an event, it may retrieve the appropriate EventPort from the EventPortRegistry server and dispatch the event. Note that a CORBA client may be served by any of the EDS sinks, and there may be more than one instance of EDS sink in the enterprise manager. Different CORBA clients may be served by different EDS sinks. In one embodiment, this is all done transparently by the existing EDS code.
A managed object initiates or generates an event. Events may include notifications, warnings, or alarms concerning a status or occurrence relating to the managed object or corresponding device. For example, an event may be generated when a monitored device experiences an error which causes it to suspend operation. Of course, events may also be generated under less critical circumstances. For example, a monitored device may generate a notification if usage of a particular resource reaches a particular threshold, such as a printer running low on toner or a background process exceeding a threshold percentage of CPU usage.
An EDS Source may receive the event through MIS. In one embodiment, the event may be transferred to the EDS Source through PMI or another suitable interface, such as a platform-specific interface. The EDS Source serves to collect all incoming events and route them to Sinks, which may act as filters to restrict the targets to which the events may be sent. The EDS Source sends the event to an EDS Sink. The EDS Sink may find the appropriate manager for the event message. The EDS Sink may query the EventPortRegistry to retrieve the corresponding event port through which to send the event. Access control checks may be performed by comparing the client manager ID with access privilege information. This ensures that the client manager is authorized to receive the event. The EDS Sink may then convert the event (as sent through PMI, for example) into a CORBA event, i.e., an event expressed in IDL. The EDS Sink may then enqueue the event in a queue corresponding to the particular manager. This queue is required to ensure ordered delivery of events to the consumer. In particular, the delivery of events may occur in the order in which the events are generated. The EDS Sink may then dispatch the event to the client.
Other objects and advantages of the invention will become apparent upon reading the following detailed description and upon reference to the accompanying drawings in which:
While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and will herein be described in detail. It should be understood, however, that the drawing and detailed description thereto are not intended to limit the invention to the particular form disclosed, but on the contrary, the intention is to cover all modifications, equivalents and alternatives falling within the spirit and scope of the present invention as defined by the appended claims.
Turning now to the drawings,
As shown in
The CPU 102 may be coupled to a network 108. The network 108 is representative of various types of possible networks: for example, a local area network (LAN), wide area network (WAN), or the Internet. The system and method for network management as disclosed herein may therefore be implemented on a plurality of heterogeneous or homogeneous networked computer systems 100 through one or more networks 108. The CPU 102 may acquire instructions and/or data for implementing system and method for network management as disclosed herein over the network 108.
Through an input/output bus 110, the CPU 102 may also coupled to one or more input/output devices that may include, but are not limited to, video monitors or other displays, track balls, mice, keyboards, microphones, touch-sensitive displays, magnetic or paper tape readers, tablets, styluses, voice recognizers, handwriting recognizers, printers, plotters, scanners, and any other devices for input and/or output. The CPU 102 may acquire instructions and/or data for implementing the system and method for network management as disclosed herein through the input/output bus 110.
The computer system 100 is operable to execute one or more computer programs. The computer programs may comprise operating system or other system software, application software, utility software, Java™ applets, and/or any other sequence of instructions. Typically, an operating system performs basic tasks such as recognizing input from the keyboard, sending output to the display screen, keeping track of files and directories on the disk, and controlling peripheral devices such as disk drives and printers. Application software runs on top of the operating system and provides additional functionality. Because applications take advantage of services offered by operating systems, and because operating systems differ in the services they offer and in the way they offer the services, an application must usually be designed to run on a particular operating system. The computer programs are stored in a memory medium or storage medium such as the memory 104 and/or ROM 106, or they may be provided to the CPU 102 through the network 108 or I/O bus 110.
In one embodiment, the computer programs executable by the computer system 100 may be implemented in an object-oriented programming language. In an object-oriented programming language, data and related methods can be grouped together or encapsulated to form an entity known as an object. All objects in an object-oriented programming system belong to a class, which can be thought of as a category of like objects which describes the characteristics of those objects. Each object is created as an instance of the class by a program. The objects may therefore be said to have been instantiated from the class. The class sets out variables and methods for objects which belong to that class. The definition of the class does not itself create any objects. The class may define initial values for its variables, and it normally defines the methods associated with the class (i.e., includes the program code which is executed when a method is invoked.) The class may thereby provide all of the program code which will be used by objects in the class, hence maximizing re-use of code which is shared by objects in the class.
In one embodiment, an enterprise manager 212 may be coupled to the CORBA gateway 208 via a proprietary or platform-dependent interface such as Portable Management Interface (PMI) 220 from Sun Microsystems, Inc. The enterprise manager 212 may include various enterprise management components such as a Management Information System (MIS), etc. Also coupled to the enterprise manager 212 via PMI 220 may be one or more PMI applications 210. PMI applications may include, for example, applications which provide access to event notification, subscription, and propagation services and access to object instance information. In one embodiment, the enterprise manager 212 may be Solstice Enterprise Manager (SEM) from Sun Microsystems, Inc., and examples of the one or more PMI applications 210 that use PMI to communicate with the SEM MIS may include SEM Viewer, SEM Alarm Manager, SEM Discovery, etc. In one embodiment, the CORBA gateway 208 may translate the CORBA manager requests 214 from IDL to PMI requests 220. Similarly, the CORBA gateway 208 may translate the enterprise manager PMI responses and PMI events 220 to IDL/IIOP responses and events 218 which may be passed on through the CORBA ORB 202 to the manager applications 206 in the form of IDL responses and CORBA events 216.
Various embodiments of the CORBA Gateway 208 may include one or more components such as a Metadata Gateway, an Event Gateway (as shown in
Furthermore, the approach improves performance and scalability by allowing event sinks to be distributed. Instead of having all clients receive their events from one event sink, the approach allows clients to receive events from different sinks, thereby providing load-balancing. In one embodiment, multiple instances of CORBA-enabled EDS sinks may be running in a single system, thereby allowing different CORBA clients to receive events from different CORBA-enabled EDS sinks. However, in a preferred embodiment CORBA clients are not aware of this multitude of CORBA-enabled EDS sinks because this feature is transparent to the clients.
Generally, the approach described below provides the capability to filter events according to criteria presented by client event subscriptions. In one embodiment, the events may be filtered to enforce policy-based access control on TMN events/notifications, determining which CORBA client applications have access to which events. The filtering of events at the sink based upon client subscriptions decreases unnecessary network traffic in that events may be "pushed" to the client, rather than delivered upon client request or the client having to filter all requests itself. This is a substantial improvement over standard polling approaches. In addition, the approach may provide easy-to-use IDL APIs that allow CORBA clients to directly subscribe/unsubscribe to events based on criteria such as object class, object instance, and event type. For example, a print manager application may subscribe to all events relating to the toner supply of laser printers of a particular make and model. The IDL APIs may allow clients to choose the format (e.g., text or ASN1) in which the events are received, which is described in more detail in the section titled "Client-Selected Format", below. The use of IDL may provide a platform-independent interface to deliver events generated by one or more managed objects to manager applications through the Event Gateway 302. Event subscriptions may be managed with services provided by an event port registry server, described below.
EventPortRegistry Server, EventPortFinder and EventPortFactory
As shown in
In one embodiment, the EventPortRegistry Server 320 includes an EventPortFactory 322, an EventPortFinder 324, and an EventPortRegistry 326. The EventPortFactory 322, EventPortFinder 324, and EventPortRegistry 326 may be implemented as CORBA objects, and the Event Gateway 302 may provide public IDL interfaces for these objects. In one embodiment, the EventPortFinder 324 and EventPortFactory 322 CORBA objects are singleton objects for the entire system (e.g., one instance of an enterprise manager). CORBA client applications may receive their events through EventPort 328 objects, which are typically created one per CORBA client application 206.
In one embodiment, EventPortFactory 322 and EventPortFinder 324 server objects may be implemented in a separate stand-alone light-weight server. This server may act as an EventPortRegistry 326 (private CORBA object). The CORBA objects (factory and finder) may be designed as tie classes that forward their requests to EventPortRegistry 326. As mentioned above, the EventPortRegistry 326 may enable client managers to subscribe and unsubscribe to various events, based upon object class, object instance, and event type.
It should be noted that EventPortRegistry 326 may be a private CORBA object to be used for inter-process communication between EDS sinks 332 and the registry. For example, when the registry process starts up, it may create the EventPortRegistry 326 CORBA object with a well-known name, "EventPortRegistry", registered with the CORBA NamingService under the name "Private:<MIS>". Then, the server may proceed to create EventPortFinder 324 with the name, "EventPortFinder" under "<MIS>" node. Finally, the server may create the EventPortFactory 322 with the name, "EventPortFactory" under "<MIS>" node. The factory and the finder may simply use the registry to create or find EventPort 328. In one embodiment, users may choose the encoding or format of the event information field of events.
EventPortRegistry 326 may then validate a ProxyAgent object reference. In one embodiment, a ProxyAgent is an entity through which a manager 206 deals with a managed object. The ProxyAgent may provide IDL methods to allow registration for events by object class, name, or event type. If the validation succeeds, then the registry will proceed with creating the port. Otherwise, an appropriate exception may be raised. After the validation succeeds, the registry may check whether the port already exists, and if so, an exception may be raised. In other words, there should be a one-to-one mapping between EventPorts 328 and Application Entity Titles (AE-Titles) in the given domain. AE-Titles are from the TMN/CCITT standards and are used to identify applications. For example, if one wants to talk to a given Event Gateway running on a given server, one could assign it an AE-Title "EGW1." Similarly, if one has a client application (or a manager application) that wants to listen or subscribe to events, it may assign itself an AE-Title so that Event Gateway 302 knows to whom to send any events when they occur. Finally, the registry may create an EventPort CORBA object 328.
Clients Registering for Events and EDS Sinks
In one embodiment, an Event Distribution Server (EDS) 330 which is coupled to the event port registry server 320 is configurable to listen for events generated by the one or more managed objects and to deliver the events to the one or more managers 206, depending upon the managers' event subscriptions and event access control.
When the EDS Sink 332 gets an event, it may retrieve the appropriate EventPort from the EventPortRegistry server and dispatch the event. Note that a CORBA client 206 may be served by any of the EDS sinks 332, and there may be more than one instance of EDS sink in the enterprise manager. Different CORBA clients may be served by different EDS sinks. In one embodiment, this is all done transparently by the existing EDS code.
In 404, an EDS Source 338 receives the event through MIS 308. In one embodiment, the event may be transferred to the EDS Source 338 through PMI or another suitable interface, such as a platform-specific interface. The EDS Source 338 serves to collect all incoming events and route them to Sinks 332, which may act as filters to restrict the targets to which the events may be sent. In 405, the EDS Source 338 sends the event to an EDS Sink 332. In 406, the EDS Sink 332 may find the appropriate manager 206 for the event message. Because the EDS Sink 332 has the AE-Title associated with the client, it may query the EventPortRegistry to retrieve the corresponding event port through which to send the event. In 408, access control checks may be performed by comparing the client manager ID with access privilege information. This ensures that the client manager 206 is authorized to receive the event. That is, the gateway may authenticate access of the manager 206 to the event. In one embodiment, the authentication may involve the use of pluggable authentication modules, described below with reference to
Event Gateway Access Control
In one embodiment, the Event Gateway 302 may provide object-level access control between manager applications and managed objects. Therefore, manager application access to managed objects may be granted at the individual object level. That is, a given manager may be granted access to particular events while being prevented from interfacing with others. In one embodiment, the client manager 206 may first be authenticated to the Event Gateway 302 by username and password, or other validation information associated with the client manager 206, which may be represented in a user profile. In one embodiment, the authentication may involve the use of pluggable authentication modules, described below with reference to
In one embodiment, this design uses thread pools to provide multiple threads delivering events to multiple consumers. If one consumer is slow in processing events, other consumers should not be adversely affected. This design allows the flexibility to assign scheduling priorities to different threads. The concurrency level of the thread pool can be configured for optimal concurrency levels (thought to be 5 or 10 on dual CPU computer systems). Thread pools are discussed in greater detail with reference to the section below entitled "Managing CORBA Events, Requests, and Replies with a Thread Pool."
Note that there may be instances when the client program may die or exit without destroying EventPorts 328. This may be intentional so that the client application 206 can come back up and continue with the old EventPort 328. In one embodiment, the only other valid signal to Event Gateway is when the event channel between the CORBA client and Event Gateway 302 is broken down, when EventPorts can be cleaned up.
An EDS sink may be initialized when a client event subscription specifies a set of filtering criteria not represented by a currently existing sink. In one embodiment, EDS sinks 332 may be initialized in the following manner. As shown in
Once a device 710 has received the requests, it may send responses back to the manager application 206. It does this by first sending the responses to the MIS 308, which passes the responses to the Request Gateway 304 in the form of PMI responses 708 via PMI 320. The Request Gateway may then translate the PMI responses 708 into platform-independent (e.g., IDL) replies 704, which are sent to the manager application 206 via IIOP 340. For example, if the request were a query for the on/off status of a printer, the response may include the value of that status. In one embodiment, client manager applications 206 may be subject to authentication by the Request Gateway 304 before access to the Request Gateway services is allowed, as well as before each request is sent. Such authentication may be performed, for example, by a pluggable authentication module, discussed below with reference to
The Request Gateway 304 may be operable to accept the management requests 702 in IDL via IIOP 340, translate them into low-level PMI 320 requests 706, and send those PMI requests to a Management Information System (MIS) 308. MIS 308 may interface with managed objects on the network by passing requests to objects and receiving responses. When MIS 308 sends back the responses 708 to the Request Gateway 304, the Request Gateway 304 translates the responses 708 into IDL replies 704 and sends the replies 704 to the CORBA client manager application 206. As used herein, the term "response" is used to refer to the PMI responses 708 that MIS 308 sends to the Request Gateway 304, whereas the term "reply" is used to refer to the IDL replies 704 that are sent to the CORBA client 206. The use of IDL/CORBA as the interface between manager applications and managed objects provides a platform-independent approach to managing object-related requests.
Security/Audit Trails
In one embodiment, the Request Gateway 304 may provide the Manager Applications 206 access to an MIS 308 service that provides security/audit trails of TMN management/object transactions. The Request Gateway 304 does this by providing a platform-independent way to turn on/off the security/audit trails via, e.g., request cmis_get/cmis_set operations on the managed object, as well as providing user information in each request sent to the MIS. The security/audit trail service provided by the MIS 308 may include a logging function which may be used to track event or request related traffic and save information such as which client sent the request/event, when the request/event occurred, and the nature of the request/event, or any other information useful for security and auditing purposes. In one embodiment, the MIS 308 security/audit service provides an "all or nothing" capability, in that either all information for all traffic may be logged, or nothing is logged. In one embodiment, the Manager Applications 206 may be subject to authentication before being allowed access to the security/audit trail service, such as by a pluggable authentication module, discussed below with reference to
In 906, the Request Gateway 304 may then spawn a new thread to run PMI's recursive dispatch in its own thread, referred to as the primary dispatcher thread 920. This design option may be employed because of the complexities and problems that may arise when the ORB and PMI loops are integrated into one loop. The individual loops may lose full functionality when they are merged, and the fact that ORB loops are multi-threaded may causes problem when the ORB loop integrated with the single-threaded PMI loop. Moreover, keeping the loops in separate threads may improve performance as CORBA requests and replies may be executed in parallel to the execution of PMI requests and responses. In the primary dispatcher thread 920, the PMI infinite loop is started in 922, and the recursive dispatch process is executed in 924.
After spawning the primary dispatcher thread 920, the Request Gateway 304 may post a callback to detect MIS disconnects. The Request Gateway 304 need not listen for managed object events because, for improved performance, it is only concerned with handling requests which originate with the manager applications 206 and the corresponding responses 708 from the managed objects. Next, in 908, the gateway initializes the ORB and, in 910, creates the ProxyAgentFinder CORBA object. In one embodiment, there may be only one instance of ProxyAgentFinder CORBA object per Request Gateway 304 instance, and each ProxyAgentFinder may be associated with only one instance of MIS 308. In one embodiment, these restrictions may be relaxed. To support multiple distributed gateways for a given MIS 308, there may be more than one Request Gateway 304 per MIS 308. After a ProxyAgentFinder object is created, it is registered with the CORBA Naming Service as "<MIS>"/"<RequestGateway Host>"/"ProxyAgentFinder". Any CORBA client wishing to connect to the Request Gateway 304 may first contact the CORBA Naming Service to get the ProxyAgentFinder CORBA object associated with the name "<MIS>"/"RequestGatewayHost"/"ProxyAgentFinder". The Request Gateway 304 may enter the ORB's infinite loop in 912.
Object-Level Access Control
In one embodiment, the Request Gateway 304 may provide object-level access control between manager applications and managed objects. Therefore, manager application access to managed objects may be granted at the individual object level. That is, a given manager may be granted access to particular objects while being prevented from interfacing with others. In one embodiment, a client manager application may be subject to authentication by the Request Gateway before being granted access to managed objects, such as by a pluggable authentication module, discussed below with reference to
In one embodiment, object-level access control may be enforced by use of a Request Service Access Point (RequestSAP). RequestSAP may be a singleton object that may be shared by all ProxyAgents. A regular application Service Access Point (SAP) does not allow the insertion of the user name in the request message to enforce object-level access control, and therefore a request SAP is recommended to send PMI requests and receive PMI responses with appropriate object-level access control enforced. When a send request is invoked, the primary response callback may be installed. This is the callback that first gets invoked for any response from the MIS 308. The primary response callback may retrieve the response message and post a secondary response callback instead of processing the callback directly. The primary response callback does not invoke a reply because the reply may directly or indirectly invoke the recursive dispatch. If this happens, the recursive dispatch may end up in deep recursion, possibly causing the process stack size to overflow and dump core. Further details of the Request Gateway's object-level access control are given below with reference to client application authentication to the Request Gateway 304, described below.
Authentication of Client Applications to the Request Gateway
In one embodiment, user information may be included with each request sent to a managed object through the MIS 308. The MIS 308 may then use this information to determine whether the user has access to that particular object. In one embodiment, the MIS 308 may check the user ID against an authentication list or table which contains user/object access information. In addition, client authentication may be performed upon client connection to the Request Gateway, described below.
Any CORBA client 206 wishing to connect to the Request Gateway 304 may first contact the CORBA Naming Service to get the ProxyAgentFinder CORBA object associated with the name "<MIS>", "ProxyAgentFinder". Then the client 206 may invoke the ProxyAgentFinder domain access IDL method to connect to the Request Gateway 304. Note that the domain access method may also be used to retrieve existing connections for that client 206. The client 206 may pass a key to the Request Gateway. In one embodiment, this key may not have any significant functionality other than identifying whether the ProxyAgent should be for OSI or SNMP management. The client 206 may then fill in the appropriate criteria (which is a list of tuples <name, value>, where <name> is an IDL string, and <value> is CORBA::Any), described in the table below according to one embodiment.
Criteria for ProxyAgents
Criteria Name
Type of Value
"domain title"
Value must be the name of the
MIS that client wants to
connect to. This criteria is
"gateway title"
Value must be the name of the
gateway (typically a host
name) that the client wants
to connect to. The value
defaults to some randomly
assigned gateway, typically
the gateway that is running
on the MIS host. This
criterion is OPTIONAL. This
criterion allows gateway
instances to be distributed
and is for future use.
"controller object"
Value must be a CORBA
object reference of
object which is created by the
manager (client) application.
This criterion is OPTIONAL.
"user profile"
Value is opaque. Its usage is
described below. Value is
used to extract the username
and password. This criterion
is MANDATORY.
"manager title"
Title used to denote the
Manager (client) which
requested access to the OSI
managed object domain. This
criterion is OPTIONAL.
In one embodiment, the related enterprise manager may be Solstice Enterprise Manager™ (SEM) available from Sun Microsystems, Inc. To maintain the same access control features that exist in SEM, the criteria may require a username and password (in encrypted form). To enable the CORBA clients to send the password in encrypted form, a wrapper library (e.g., implemented in C++) may be provided which contains an encryption function similar to that currently used in PMI 320. The client may pass in CORBA 'any' which contains the user profile (opaque to the CORBA Gateway 208). In one embodiment, a class library may be provided to allow pluggable authentications, described below with reference to
In one embodiment, a client application 206 may provide its own authentication interface in the form of a pluggable authentication module, described below with reference to
The Request Gateway 304 may then send a create request for an application instance object. The create request may contain the client's username. This request may be used to subject the client 206 to object-level access control. To do this, the Request Gateway 304 may create a RequestSAP to send the request, as described above. If the creation succeeds, then the Request Gateway 304 may proceed to create a Proxy Agent CORBA object, store it in a proxy agent list, and return a reference to it to the client 206; otherwise, an exception may be raised.
The Proxy Agent may store the key and criteria. When a destroy function is called on the Proxy Agent, a client-implemented Proxy Agent Controller may be contacted to determine whether the destruction may be allowed. If allowed, the Proxy Agent object may be destroyed, after which the Proxy Agent Controller object may be destroyed. The purpose of the Proxy Agent Controller is to notify the client application 206 when the Proxy Agent is about to be destroyed, as well as when destruction has occurred.
Client-Selected Format
As mentioned above, in some embodiments, the client 206 may choose the format in which to send and receive information such as events, requests, notifications, etc. To provide text based requests and replies, an extension IDL interface may be used. For example, a new IDL interface may be provided which extends ProxyAgent. The tie mechanism may be used to create the concrete version of the ProxyAgent object. The extensions may allow clients to send requests and receive replies using values in text form rather than in CORBA::Any (i.e., ASN1 <any>). The text form values may retain the same format as that of PMI.
The JIDM standard does not explicitly mandate the IDL format of events. In one embodiment, the following IDL may be used for event reports:
struct EventReport {
Note that the CORBA ASN1 generic data type <any> is used to store event information. For receiving event_info in a string format for text-based events, the following structure may be used:
struct EventReport {
Note the use of the <string> data type for storing the event information. The use of text format may greatly reduce the network traffic related to requests and responses. It should be noted that in other embodiments, various other data formats may be used to store event information.
Managing CORBA Events, Requests, and Replies with a Thread Pool
In one embodiment, the Event Gateway 302 and the Request Gateway 304 may be designed as multi-threaded systems. A mechanism may be provided to prevent any single client 206 from overloading the system, including denial of service attacks. A thread pool may be used to minimize thread creation and deletion inefficiencies. If a client sends an excessive number of requests to the system, the client may be assigned only one thread from the thread pool in order to preserve resources for other clients. In one embodiment, there may be one thread pool (reply thread pool) per Request Gateway 304. This reply thread pool may initially have a concurrency of 3. The thread pool may enhance the performance of sending replies to clients because the send reply method may be a blocking call. A thread pool may improve the response time to different CORBA clients 206 even in the presence of a few slow CORBA clients 206, in that the slow CORBA clients 206 may be isolated in their respective threads away from the other clients.
In one embodiment, each ProxyAgent instance may have a reply dispatcher, which may schedule replies to that particular client 206 in sequential order (the same order in which the client 206 issued the requests). In this way, message ordinality may be preserved. Similarly, the client 206 may receive replies for a given request before receiving any replies for any subsequent requests. One approach to preserving message order in a thread-safe manner is through the use of a synchronous task scheduler with the thread pool, described below.
To ensure ordered delivery of events or replies to the CORBA gateway clients in a multi-threaded environment using a thread pool, a synchronous task scheduler may be used. The primary utility of the synchronous task scheduler is that it leverages the efficiency and scalability of a thread pool while preserving the order of events, requests, and replies. There may be a synchronous task scheduler associated with each client manager to preserve the chronology of messages sent to each.
When messages are to be delivered serially to the client manager application 206, such messages may be scheduled by the synchronous task scheduler 1002. The synchronous task scheduler may maintain an internal message list, and deliver one message at a time from that internal list. The synchronous task scheduler 1002 may hold a reference to a thread pool and use that thread pool to deliver messages.
In one embodiment, the Event Gateway 302 may use task schedulers 1002 to deliver managed object events serially to client managers, assigning a task scheduler 1002 to each client manager connected to the Event Gateway 302. Similarly, the Request Gateway 304 may use task schedulers to serially deliver managed object replies (to requests sent by the client managers 206) to the client managers 206, such that the replies are received by the client managers 206 in the same order the corresponding requests were sent. The Request Gateway 304 may also assign a task scheduler 1002 to each client manager connected to the Request Gateway 304.
In 1105, the synchronous task scheduler completes the delivery of a prior message, if there is one. In one embodiment, when the synchronous task scheduler receives a message, it may determine if any prior message is currently being delivered. If no prior message is currently being delivered, the synchronous task scheduler may deliver the current message immediately, rather than enqueueing the message on the message list for later delivery.
In 1106, the synchronous task scheduler dequeues the current message. Note that the use of a queue for the message list ensures that messages will be processed in the order in which they are received, because the queue is a first in, first out (FIFO) data structure.
Then, in 1108, an available thread is assigned from the thread pool for delivery of the message. Finally, in 1110, the scheduler may initiate delivery of the message, sending the message to the client manager application.
In one embodiment, when the synchronous task scheduler sends a message to the client manager, it may wait until it receives an acknowledgement of receipt from the client manager before dispatching the next message. This may be necessary because each sequential message may be delivered with a different thread, and because some threads may execute more rapidly than others, a first thread execution which is initiated before a second thread execution may actually finish after the second thread completes its execution. By restricting the messages of a particular scheduler to be delivered one at a time, the message chronology for a given client manager may be maintained.
As shown in
Also shown in
In one embodiment, the client-side library 1208 is implemented in accordance with a specification expressed in an interface definition language (IDL). The interface definition language may be operable to define object interfaces across a plurality of platforms and across a plurality of programming languages. The client-side library 1208 may also be implemented for the particular client platform corresponding to the client computer system 1206. As used herein, a "platform" includes a combination of a particular operating system, programming language, software development environment, and/or set of computing hardware for which software may be developed. The server-side library 1204 may also be implemented in accordance with the specification expressed in the interface definition language and implemented for a particular server platform corresponding to the server computer system 1202.
In one embodiment, the IDL interface for authentication may include the following AuthenticationServer and AuthenticationClient classes:
class AuthenticationServer {
virtual CORBA::Boolean decrypt_user_profile(
const CORBA::Any& user_profile_blob,
RWCString& user_name,
RWCString& password
) throw( ) = 0;
class AuthenticationClient {
virtual CORBA::Any_ptr encrypt_user_profile(
const char* user_name,
char* password,
const char* key
) throw( ) = 0;
virtual CORBA::Any_ptr get_user_profile(
CosNaming::NamingContext_var root_nc,
const char* key
) throw( ) = 0;
In one embodiment, the client-side authentication library 1208 implements the AuthenticationClient class. For example, the client-side authentication library 1208 may implement the AuthenticationClient class using NES DES encryption. In one embodiment, the server-side authentication library 1208 implements the AuthenticationServer class. For example, the server-side authentication library 908 may implement the AuthenticationServer class using an SEM Authentication daemon to validate the DES-encrypted user identity.
In one embodiment, the server-side authentication library 1204 may be implemented in C++. The client-side authentication library 1208 may be implemented in any programming language for which there is an IDL mapping, i.e., any programming language in which the IDL interface specification mentioned above may be implemented.
In one embodiment, the client-side authentication library 1208 and the server-side authentication library 1204 may be implemented as shared dynamic libraries, allowing the client-side authentication library to be shared by a plurality of management applications and the server-side authentication library to be shared by a plurality of gateway components.
As 1406 indicates, a user profile may be encrypted by the client-side authentication library, as specified by the client-specified and implemented encryption scheme. Then, as indicated by 1408, the server-side authentication library retrieves the encrypted user profile. At 1410 the server-side authentication library then decrypts the user profile. With the resulting information, the authentication status of the user may be determined, as indicated in 1412. In one embodiment, this process may be used to authenticate management requests for managed objects sent by manager applications.
The fact that the authentication system may be implemented as pluggable modules makes the system extremely flexible and extensible. In one embodiment, default versions of the client-side authentication library and the server-side authentication library may be provided so that the client user need not implement his own authentication scheme unless he specifically wishes to do so.
Various embodiments may further include receiving or storing instructions and/or data implemented in accordance with the foregoing description upon a carrier medium. Suitable carrier media may include storage media or memory media such as magnetic or optical media, e.g., disk or CD-ROM, as well as transmission media or signals such as electrical, electromagnetic, or digital signals, conveyed via a communication medium such as network 108 and/or a wireless link.
While the present invention has been described with reference to particular embodiments, it will be understood that the embodiments are illustrated and that the invention scope is not so limited. Any variations, modifications, additions and improvements to the embodiments described are possible. These variations, modifications, additions and improvements may fall within the scope of the invention as detailed within the following claims.
|Cited Patent
|Filing date
|Publication date
|Feb 1, 1993
|Apr 11, 1995
|National Semiconductor Corporation
|Interenterprise electronic mail hub
|Jan 8, 1993
|Sep 19, 1995
|Digital Equipment Corporation
|Method and apparatus for allocating server access in a distributed computing environment
|Jun 3, 1994
|Apr 23, 1996
|The United States Of America As Represented By The Secretary Of The Navy
|Intermediate network authentication
|Feb 12, 1993
|Dec 17, 1996
|Digital Equipment Corporation
|Method and apparatus for authenticating a client to a server in computer systems which support different security mechanisms
|Feb 7, 1994
|May 20, 1997
|International Business Machines Corporation
|Cross address space thread control in a multithreaded environment
|Sep 1, 1995
|Jul 8, 1997
|Lucent Technologies Inc.
|Synchronization of mailboxes of different types
|Jun 7, 1995
|Jan 13, 1998
|Open Market, Inc.
|Internet server access control and monitoring systems
|Sep 15, 1994
|Mar 24, 1998
|Visual Edge Software Limited
|System and method for providing interoperability among heterogeneous object systems
|Nov 13, 1995
|Dec 8, 1998
|Sun Microsystems, Inc.
|Network topology management system through a database of managed network resources including logical topolgies
|Dec 19, 1996
|Feb 9, 1999
|Dset Corporation
|Automatic translation between CMIP PDUs and custom data structures
|Aug 9, 1996
|Apr 6, 1999
|Sun Microsystems, Inc.
|Interface for telecommunications network management
|Dec 29, 1995
|Aug 24, 1999
|Nokia Telecommunication Oy
|Method for comparing attribute values of controllable object expressions in a network element
|Nov 25, 1997
|Sep 14, 1999
|Sun Microsystems, Inc.
|Method and apparatus for run-time memory access checking and memory leak detection of a multi-threaded program
|Dec 31, 1996
|Oct 26, 1999
|Compaq Computer Corporation
|Scoreboard for cached multi-thread processes
|Aug 15, 1997
|Nov 9, 1999
|Alcatel Alsthom Compagnie Generale D'electricite
|Process for managing the naming of objects, process for mapping an object name to a CORBA object reference, program module, computer unit, and computer system
|Jul 22, 1997
|Nov 16, 1999
|Cyva Research Corporation
|Personal information security and exchange tool
|Oct 4, 1996
|Jan 25, 2000
|International Business Machines Corporation
|Framework for object-oriented interface to record file data
|Apr 16, 1998
|Feb 8, 2000
|Unisys Corp.
|Computer-implemented method for generating distributed object interfaces from metadata
|Jan 9, 1998
|Mar 28, 2000
|Sun Microsystems, Inc.
|System and method for a distributed debugger for debugging distributed application programs
|Mar 3, 1998
|Jul 4, 2000
|Nec Corporation
|Agent identification device, agent device with program reception function, and network system
|Nov 24, 1997
|Jan 23, 2001
|International Business Machines Corporation
|System and method for generating unsupported network information indicators
|Jul 30, 1998
|Mar 13, 2001
|Mutek Solutions, Ltd.
|System and method for remotely analyzing the execution of computer programs
|Feb 19, 1998
|Mar 20, 2001
|Ameritech Corporation
|System and method for executing a request from a client application
|Jun 8, 1998
|Mar 27, 2001
|Adc Telecommunications, Inc.
|Visual data integration system and method
|Nov 13, 1997
|Mar 27, 2001
|Sun Microsystems, Inc.
|Service framework for a distributed object network system
|May 17, 1996
|Jun 12, 2001
|Sun Microsystems, Inc.
|Method and apparatus for disposing of objects in a multi-threaded environment
|Oct 12, 1993
|Aug 21, 2001
|Intel Corporation
|Server/client architecture and method for multicasting on a computer network
|Aug 20, 1997
|Aug 28, 2001
|Method for supporting address interaction between a first entity and a second entity, converter for address interaction, and computer system
|Jul 30, 1998
|Aug 28, 2001
|Mutek Solutions, Ltd.
|System and method for monitoring and analyzing the execution of computer programs
|Sep 3, 1996
|Sep 11, 2001
|Insession Inc.
|System, method and article of manufacture for transaction processing and monitoring of independent interacts
|Dec 4, 1998
|Oct 2, 2001
|Sun Microsystems, Inc.
|Event distribution system for computer network management architecture
|Apr 14, 1998
|Nov 13, 2001
|Method of providing a service to users of a telecommunication network, service control facility, and processing node
|Sep 9, 1998
|Nov 20, 2001
|Sanctum Ltd.
|Method and system for protecting operations of trusted internal networks
|Dec 23, 1999
|Nov 27, 2001
|Gte Service Corporation
|Secure gateway having user identification and password authentication
|Jun 23, 1998
|Dec 11, 2001
|Ameritech Corporation
|Global service management system for an advanced intelligent network
|Mar 17, 1998
|Jan 29, 2002
|Fujitsu Limited
|Communication link information generating device, a three-tier client/server system, and a medium storing a communication link information generator program
|Oct 15, 1999
|Mar 12, 2002
|Silverstream Software, Inc.
|Connection concentrator for distributed object systems
|May 31, 1998
|Mar 26, 2002
|Lucent Technologies, Inc.
|Method for computer internet remote management of a telecommunication network element
|Feb 22, 1999
|Apr 23, 2002
|International Business Machines Corporation
|Debugger thread synchronization control points
|Feb 22, 1999
|Apr 23, 2002
|International Business Machines Corporation
|Debugger thread identification points
|Dec 31, 1998
|Sep 3, 2002
|Nortel Networks Limited
|Abstract interface for media and telephony services
|May 7, 1999
|Oct 15, 2002
|Samsung Electronics Co., Ltd.
|Method and system for device to device command and control in a network
|Jun 3, 1999
|Oct 15, 2002
|Microsoft Corporation
|Method and apparatus for analyzing performance of data processing system
|Nov 1, 1999
|Dec 17, 2002
|Sun Microsystems, Inc.
|System and method for generating code for query object interfacing
|Jun 2, 1999
|Mar 4, 2003
|International Business Machines Corporation
|Method for optimizing locks in computer programs
|Dec 16, 1999
|Mar 25, 2003
|International Business Machines Corporation
|Method, system, and program for logging statements to monitor execution of a program
|May 7, 1999
|Apr 8, 2003
|Richard Humpleman
|Method and apparatus for user and device command and control in a network
|Jun 19, 2000
|Feb 17, 2004
|Korea Telecommunication Authority
|Communication apparatus and method between distributed objects
|Apr 21, 2000
|Jan 4, 2005
|Sun Microsystems, Inc.
|Synchronous task scheduler for corba gateway
|" Inter-Domain Management: Specification Translation,", The Open Group, 1997, 281 pages.
|"A CORBA Primer," Technical Overview, A White Paper, Segue Software, 7 pages.
|"A Discussion of the Object Management Architecture," Object Management Group, Inc., Jan. 1997, pp. 1-1 to 1-6, 2-1 to 2-6, 3-1 to 3-8, 4-1 to 4-12, A-1 to A-8.
|"CMIS/C++: Application Programming Interface," Network Management Forum, Issue 1.0, Feb. 1998, pp. 1-226.
|"CORBA Overview," Object Management Group, Inc., 1995, 13 pages.
|"CORBA-Based Telecommunication Network Management Systems," Object Management Group, Inc., May 1996, pp. 1-29.
|"Development Environment," Sun Microsystems, Inc., 1994-2000, 11 pages.
|"Intelligent Networking with CORBA, A White Paper," Nortel, et al., Draft 2.0, Oct. 31, 1996, pp. 1-7.
|"Inter-Domain Management Between CORBA and SNMP: WEB-Based Management-CORBA/SNMP Gateway Approach," Subrata Mazumdar, Lucent Technologies, 1996, pp. 1-16.
|"Java, RMI and CORBA," Object Management Group, Inc., 1997-1999, 8 pages.
|"JIDM Interaction Translation," Final Submission to OMG's CORBA/TMN Interworking RFP, Object Management Group, Inc. Edition 4.3, OMG Document No.: telecom/98-10-10, Oct. 1998, 273 pages.
|"Joint Inter Domain Management (JIDM)," The Open Group, Jan. 10, 2000, 5 pages.
|"Mapping of Common Management Information Services to CORBA Objects Services Specification," Subrata Mazumdar, Lucent Technologies, Mar. 10, 1997, pp. 1-68.
|"Overview of CORBA," Object Management Group, Inc., Jan. 19, 2000, 4 pages.
|"Solstice Enterprise Manager 2.1 Reviewr's/Evaluator's Guide for Telecommunications Network Management," Sun Microsystems, Inc., 1998, pp. 1-45.
|"Solstice Enterprise Manager 2.1: A Technical White Paper,", Sun Microsystems, Inc. Chapters 1-6, 68 pages, 1997.
|"Solstive Enterprise Manager 3.0: Satisfying the Needs of Telecom Carriers & Services Providers," Sun Microsystems, Inc., 1994-2000, 3 pages.
|"Specification of Abstract Syntax Notation One (ASN.1)," International Telecommunication Union, ITU-T Recommendation X.208, 1988 and 1993, pp. 1-72.
|"Specification of Basic Encoding Rules for Abstract Syntax Notation One (ASN.1)," International Telecommunication Union, ITU-T Recommendation X.209, 1988 and 1993, pp. 1-23.
|"What is CORBA?," Object Management Group, Inc., 1997-1999, 2 pages.
|Guy Genilloud, "An Analysis of the OSI Systems Management Architecture from an ODP Perspective," IEEE, 1996, pp. 72-81.
|N. Lynch, et al., "Web Enabled TMN Manager," Telecommunications, Conference Publication No. 451, Apr. 1, 1998, pp. 121-126.
|Citing Patent
|Filing date
|Publication date
|Oct 1, 2001
|Sep 26, 2006
|Microsoft Corporation
|Programming framework including queueing network
|Feb 14, 2001
|Feb 20, 2007
|Cisco Technology, Inc.
|Method and apparatus for mapping network events to names of network devices
|Sep 30, 2002
|Mar 13, 2007
|Bellsouth Intellectual Property Corp.
|Health checker for EMS CORBA notification listener
|Jan 31, 2003
|Apr 17, 2007
|Aepona Limited
|Gateway for interaction of telecommunications network resources and applications
|Oct 1, 2001
|May 22, 2007
|Microsoft Corporation
|Generic communications framework
|Sep 30, 2002
|Jul 17, 2007
|Bellsouth Intellectual Property Corp.
|NMS CORBA listener for EMS signals
|May 20, 2004
|Oct 14, 2008
|Taiwan Semiconductor Manufacturing Company, Ltd.
|System and method for improving equipment communication in semiconductor manufacturing equipment
|Sep 15, 2003
|Feb 10, 2009
|Taiwan Semiconductor Manufacturing Co., Ltd.
|System and method for defining interface of manufacture execution system
|Sep 30, 2002
|Jun 2, 2009
|At&T Intellectual Property I, L.P.
|Systems and methods for updating EMS class object references
|Jul 7, 2009
|International Business Machines Corporation
|Method and apparatus for controlling data flows in distributed storage systems
|Mar 2, 2010
|3Com Corporation
|Apparatus and method for processing data relating to events on a network
|Aug 10, 2010
|Bea Systems, Inc.
|System and method for concentration and load-balancing of requests
|Dec 14, 2010
|Cisco Technology, Inc.
|Approach for canceling events
|Dec 21, 2010
|Cisco Technology, Inc.
|Method and apparatus providing device-initiated network management
|Apr 10, 2004
|Aug 23, 2011
|Abb Research Ltd
|Method and system for event transmission
|Feb 24, 2006
|Jan 24, 2012
|Rockwell Collins, Inc.
|Universal data forwarding system and method
|Jul 28, 2010
|Apr 24, 2012
|Oracle International Corporation
|System and method for achieving scalability in domain computing
|Nov 12, 2010
|Oct 16, 2012
|Cisco Technology, Inc.
|Method and apparatus providing device-initiated network management
|Nov 6, 2012
|Twilio, Inc.
|System and method for processing telephony sessions
|Mar 2, 2010
|Nov 20, 2012
|Twilio, Inc.
|Method and system for a multitenancy telephone network
|Sep 6, 2007
|Feb 19, 2013
|International Business Machines Corporation
|Apparatus, system, and method for visual log analysis
|Jun 23, 2011
|Apr 9, 2013
|Twilio, Inc.
|Method for providing clean endpoint addresses
|May 19, 2011
|Aug 13, 2013
|Twilio, Inc.
|Method and system for a multitenancy telephony network
|Jan 16, 2013
|Oct 29, 2013
|Twilio, Inc.
|Method and system for a multitenancy telephone network
|Oct 7, 2010
|Nov 12, 2013
|Twilio, Inc.
|System and method for running a multi-module telephony application
|Jun 6, 2013
|Dec 3, 2013
|Twilio, Inc.
|System and method for managing latency in a distributed telephony network
|Sep 28, 2009
|Dec 17, 2013
|Twilio, Inc.
|System and method for processing media requests during a telephony sessions
|Feb 4, 2011
|Feb 11, 2014
|Twilio, Inc.
|Method for processing telephony sessions of a network
|Jun 28, 2005
|Apr 1, 2014
|Oracle America, Inc.
|Methods and apparatus for remote management and self management of servers
|Oct 1, 2012
|May 27, 2014
|Twilio, Inc.
|Method and system for a multitenancy telephone network
|Jul 24, 2013
|May 27, 2014
|Twilio, Inc.
|Method and system for preventing illicit use of a telephony platform
|Jul 25, 2013
|May 27, 2014
|Twilio, Inc.
|Method and system for controlling message routing
|Jan 16, 2013
|Jun 17, 2014
|Twilio, Inc.
|System and method for processing telephony sessions
|Jan 16, 2013
|Sep 16, 2014
|Twilio, Inc.
|System and method for processing telephony sessions
|Jun 27, 2011
|Sep 16, 2014
|Twilio, Inc.
|System and method for enabling real-time eventing
|Oct 15, 2013
|Jan 20, 2015
|Twilio, Inc.
|System and method for triggering on platform usage
|Oct 15, 2013
|Feb 3, 2015
|Twilio, Inc.
|System and method for routing communications
|Oct 1, 2009
|Feb 24, 2015
|Twilio, Inc.
|Telephony web event system and method
|Jan 17, 2014
|Mar 31, 2015
|Twilio, Inc.
|Method and system for a multitenancy telephone network
|Mar 13, 2014
|Apr 7, 2015
|Twilio, Inc.
|System and method for improving routing in a distributed communication platform
|Sep 17, 2014
|Sep 15, 2015
|Twilio, Inc.
|System and method for providing communication platform metadata
|May 8, 2014
|Oct 13, 2015
|Twilio, Inc.
|System for transforming media resource into destination device compatible messaging format
|Nov 11, 2013
|Dec 8, 2015
|Twilio, Inc.
|System and method for running a multi-module telephony application
|Jun 19, 2014
|Dec 29, 2015
|Twilio, Inc.
|System and method for providing a communication endpoint information service
|Apr 17, 2015
|Dec 29, 2015
|Twilio, Inc.
|System and method for enabling multi-modal communication
|Sep 29, 2009
|Jan 5, 2016
|International Business Machines Corporation
|Formalizing, diffusing and enforcing policy advisories and monitoring policy compliance in the management of networks
|May 15, 2014
|Jan 19, 2016
|Twilio, Inc.
|System and method for managing media in a distributed communication network
|May 8, 2014
|Jan 19, 2016
|Twilio, Inc.
|System and method for transmitting and receiving media messages
|Jul 6, 2015
|Jan 26, 2016
|Twilio, Inc.
|System and method for managing conferencing in a distributed communication network
|Jun 19, 2013
|Jan 26, 2016
|Twilio, Inc.
|System and method for queuing a communication session
|Jul 7, 2015
|Feb 2, 2016
|Twilio, Inc.
|Method and system for applying data retention policies in a computing platform
|Jan 14, 2014
|Feb 2, 2016
|Twilio, Inc.
|System and method for offering a multi-partner delegated platform
|Apr 15, 2014
|Feb 23, 2016
|Twilio, Inc.
|Method and system for preventing illicit use of a telephony platform
|Mar 13, 2014
|Mar 8, 2016
|Twilio, Inc.
|System and method for integrating session initiation protocol communication in a telecommunications platform
|Dec 11, 2013
|Apr 5, 2016
|Twilio, Inc.
|System and method for processing media requests during telephony sessions
|Dec 18, 2014
|Apr 5, 2016
|Twilio, Inc.
|System and method for routing communications
|Dec 12, 2014
|Apr 19, 2016
|Twilio, Inc.
|System and method for triggering on platform usage
|Sep 17, 2014
|Apr 26, 2016
|Twilio, Inc.
|System and method for enabling dynamic multi-modal communication
|Jul 2, 2001
|Oct 31, 2002
|Stevenson David James
|Apparatus and method for processing data relating to events on a network
|Jan 24, 2002
|Aug 28, 2003
|Jyri Lankinen
|Method and system where one thread can handle several different services concurrently
|Jan 31, 2003
|Sep 18, 2003
|Mcquillan Liam
|Gateway for interaction of telecommunications network resources and applications
|May 20, 2003
|Oct 23, 2003
|George Feinberg
|File Storage system having separation of components
|Sep 15, 2003
|Sep 23, 2004
|Huang Hwa Shin
|System and method for defining interface of manufacture execution system
|Jan 30, 2004
|Oct 28, 2004
|Device for the control of heterogeneous equipment in a telecommunication network
|Jul 24, 2003
|Jan 27, 2005
|Bolar Daniel Roy
|Corba gateway
|Mar 10, 2003
|Nov 17, 2005
|Thomson Licensing S.A.
|Method for updating a web client on a non ip based home network, and devices for implementing the process
|May 20, 2004
|Nov 24, 2005
|Taiwan Semiconductor Manufacturing Co., Ltd.
|System and method for improving equipment communication in semiconductor manufacturing equipment
|Jul 20, 2004
|Jan 26, 2006
|International Business Machines Corporation
|System and method for presenting chat QoS indication to user
|Oct 31, 2005
|Mar 30, 2006
|Bea Systems, Inc.
|System and method for concentration and load-balancing of requests
|Apr 10, 2004
|Oct 5, 2006
|Abb Research Ltd.
|Methods and system for event transmission
|Apr 19, 2005
|Oct 19, 2006
|International Business Machines Corporation
|Method and apparatus for controlling data flows in distributed storage systems
|Dec 22, 2006
|Jun 7, 2007
|Sony Antony
|Nms corba listener for ems signals
|Jul 11, 2005
|Dec 18, 2008
|Michael Berger
|Network Management Using Peer-to-Peer Protocol
|Sep 6, 2007
|Mar 12, 2009
|Ezequiel Cervantes
|Apparatus, system, and method for visual log analysis
|Sep 29, 2009
|Jan 21, 2010
|Bigfix, Inc.
|Formalizing, diffusing and enforcing policy advisories and monitoring policy compliance in the management of networks
|Sep 28, 2009
|Jun 10, 2010
|Jeffrey Lawson
|System and method for processing media requests during a telephony sessions
|Oct 1, 2009
|Jun 17, 2010
|Jeffrey Lawson
|Telephony Web Event System and Method
|Mar 2, 2010
|Sep 16, 2010
|Jeffrey Lawson
|Method and system for a multitenancy telephone network
|Jan 20, 2011
|Bea Systems, Inc.
|System and method for achieving scalability in domain computing
|Mar 10, 2011
|Burjiz Pithawala
|Method and apparatus providing device-initiated network management
|Apr 7, 2011
|Jeffrey Lawson
|System and method for running a multi-module telephony application
|Oct 7, 2010
|Apr 7, 2011
|Jeffrey Lawson
|System and method for mitigating a denial of service attack using cloud computing
|Oct 6, 2009
|Dec 29, 2011
|Essilor International (Compagnie Generale D'optique)
|Processing Device for Processing an Order Request of an Ophthalmic Lens
|Oct 17, 2007
|Aug 24, 2011
|Processing method for telecommunication network management message
|U.S. Classification
|709/223, 709/224, 709/228, 370/254, 710/20
|International Classification
|Cooperative Classification
|European Classification
|Aug 11, 2000
Owner name: SUN MICROSYSTEMS, INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ALLAVARPU, SAI V.;BHAT, SHIVARAM;REEL/FRAME:010993/0884;SIGNING DATES FROM 20000515 TO 20000522
|Aug 5, 2009
|Fee payment
Year of fee payment: 4
|Mar 14, 2013
|Fee payment
Year of fee payment: 8
|Dec 14, 2015
Owner name: ORACLE AMERICA, INC., CALIFORNIA
Free format text: MERGER AND CHANGE OF NAME;ASSIGNORS:ORACLE USA, INC.;SUN MICROSYSTEMS, INC.;ORACLE AMERICA, INC.;REEL/FRAME:037280/0199
Effective date: 20100212


text:
MacBook power cord 5 pins Magsafe connector and cable Replacement A weakness of the MacBook is it's power cord failure after some times. it become a panicking moment when you cannot charge you MacBook anymore. It brick's it! So at the first sing of little orange or green light not showing when plugged, Just replace it! https://d3nevzfk7ii3be.cloudfront.net/igi/w2KWLEVUBPlKtILl Pierre Merineau 15 - 30 minutes Difficult Apple AC Adapter
In this guide we will change the part of the charger that connect to the computer. you can find this cable on Ebay.

If the broken part is near the transfo, you could easily use the same cord but a bit shorter and you will have to find a way to make a grommet or reuse the old one.
 2014-03-03T10:57:18-07:00 This guide has been found to be exceptionally cool by the iFixit staff. An awesome member of our community made this guide. It is not managed by iFixit staff. The Tools: A decent welding pen A wire cutter A lead vacuum pump A big heavy duty spudger A pair of snap-ring pliers installed for external snap-ring. Any long nose would do, this is just perfect for the job if you happen to have a pair :-) Super glue 1 or 2 pair of small clamps https://d3nevzfk7ii3be.cloudfront.net/igi/w2KWLEVUBPlKtILl Open the reeling flaps Insert the pliers and pry slowly The flaps will fall Do the same on the other side Slowly! https://d3nevzfk7ii3be.cloudfront.net/igi/cQQYWRbV3NDYiaEx https://d3nevzfk7ii3be.cloudfront.net/igi/Wn5ERN4WMjCDECXY https://d3nevzfk7ii3be.cloudfront.net/igi/5DOOH5pskEuoBNHo Finish it by hand Apply decent force At some point it will crack open. https://d3nevzfk7ii3be.cloudfront.net/igi/iYSaL2tLXoow1hFE https://d3nevzfk7ii3be.cloudfront.net/igi/sLW21VgpdhZBmRkS Carefully remove the inside from the shell You may find the metallic sheeting to break a little, it's ok! https://d3nevzfk7ii3be.cloudfront.net/igi/ALTZxfSK2LCOWZWE I like to insert a big spudger to give room so I can work. https://d3nevzfk7ii3be.cloudfront.net/igi/tvuryRNbaYhpeeLp Make sure you note the position of the positive and negative. I like to start by removing a bit of lead with the pump Separate the cables, it may require some force, but be careful not to break the board. https://d3nevzfk7ii3be.cloudfront.net/igi/QSfpXdvOxKPwJeMk https://d3nevzfk7ii3be.cloudfront.net/igi/faiIGABALlT4x2XA https://d3nevzfk7ii3be.cloudfront.net/igi/Y3TD4NAeDwMYNAbi The replacement cable should come already soldered I like to bend it 90 degrees to help insertion https://d3nevzfk7ii3be.cloudfront.net/igi/1OPjklvyeSqBDnBB https://d3nevzfk7ii3be.cloudfront.net/igi/BJSnIbSHeBlEFWhB Carefully put back the transfo in the shell It will be tight! https://d3nevzfk7ii3be.cloudfront.net/igi/wElmlgQiqniCFoHS Place the cable grommet in the proper position https://d3nevzfk7ii3be.cloudfront.net/igi/ScXYmYpKkNbEJOet Put the flappers back in position https://d3nevzfk7ii3be.cloudfront.net/igi/2VE4UinmInKOKYkX Put some super glue on the cover Avoid the flaps areas and the grommet area https://d3nevzfk7ii3be.cloudfront.net/igi/Zy6uJ1CtXpLrPsJd Keeping the flaps in place put the cover on top. It will be tight, be patient! Make sure the flaps stays in place. You might want to wear gloves, since you are manipulating super glue, you might end up with some on your fingers. https://d3nevzfk7ii3be.cloudfront.net/igi/gGr323INXdImeUu1 https://d3nevzfk7ii3be.cloudfront.net/igi/FRq2CLXKbLCMBelN https://d3nevzfk7ii3be.cloudfront.net/igi/35LVTL5dVBFqhPFL I like to finish closing by clamping. Let it rest for the super glue to set https://d3nevzfk7ii3be.cloudfront.net/igi/idUdpem66QDxZeZB https://d3nevzfk7ii3be.cloudfront.net/igi/uAHGHSHnKRehEQL3 Like new The only clue that you made something there is the cleanliness of the cable :-) https://d3nevzfk7ii3be.cloudfront.net/igi/dK3QbtxbboGabwH5
Apply and repeat to all your friends victim of faulty cable ;-)
 2014-02-02T19:22:22-07:00


text:
How to find the fry?
Well, my platy gave birth today (to at least one). I saw one by the heater, but then it swam away. And now I can't find it at all. So my question is, how do you actually find them?
if u havent found it yet then it might have got eaten but i hope thats not it. is the tank planted?
I am probably too late, but there's lots of places that you can usually find the babies. Mostly, you can find them hiding in the plastic or real plants... look all over the leafs! Lots of times I see mine sitting inside the leafs! Also, if you have any fine looking plants such as java moss or something like what I had in my fish tank (picture 35 attached!) those are gold mines for finding baby fish! :-P Also, lots of times they hide in the gravel if you have larger gravel pieces. Swish your hand around it to create a current near the rocks so they get sucked out. If you have some floating plants, those are also "gold mines" for finding baby fish! :p (picture 41). I found most of my baby fish in the red plant or the floating plants I've shown you. Just look in all the possible tiny hiding places you can. When you find one, don't take your eyes off it. Get a net, and coax it into a corner or against the glass so you can get it into the net. You can also use some tubing that is small, like the tubing for an air pump, create a suction, and use it to suck up the baby fish. cover it with your finger when ur not using it so the water doesn't just keeping filling up. use a bucket and suck them into it.
I hope that you can find some!!! goodluck! let us know how it goes.
ALL the guppy fry i have ever found have been sat on the gravel....except 1 that was behind the heater :):):)
i found mine sitting on the gravel
|All times are GMT -5. The time now is 07:42 PM.
Powered by vBulletin® Version 3.7.4
Copyright ©2000 - 2016, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.6.0 PL2