sudo gedit /etc/wvdial.conf

[Dialer Defaults]
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Modem Type = Analog Modem
ISDN=0
Phone = *99***1#
Username = <Phone number>
Password = <Phone number>
New PPPD = yes
Modem = /dev/ttyUSB0
Baud = 406800
Stupid Modem = 1


3. Run wvdial

sudo wvdial

To enable general debug logs add the below line

 -Djacorb.log.default.verbosity=4

To enable notification debug logs add the below line

 -Dorg.jacorb.notification.log.verbosity=4

To increase POA Queue. Increase this parameter, for connecting with many EMSs or for many parallel requests. Default value is 100

 -Djacorb.poa.queue_max=100

thread pool configuration for request processing

 -Djacorb.poa.thread_pool_max=100
 -Djacorb.poa.thread_pool_min=20

@Entity public class TestEntity {
   @Enumerated(EnumType.STRING)   
   @Column(name="ENUM_TYPE")   
   private TestEnum testEnum; 
}

Using XML Based Mapping :   Add  hibernate-annotations.jar in your classpath during deployment but there’s no compile-time dependency:

<property name="testEnum" length="30" column="testEnum" lazy="false">
<type name="org.hibernate.type.EnumType">
<param name="enumClass">test.TestEnum</param>
<param name="type">12</param> <!-- To store enum value as VARCHAR -->
</type>
</property>

http://nms.gdd.net/index.php/Main_Page

http://docwiki.cisco.com/wiki/Internetworking_Technology_Handbook

SNMP

http://docwiki.cisco.com/wiki/Simple_Network_Management_Protocol

Books

http://www.amazon.com/SNMP-SNMPv2-RMON-Practical-Management/dp/0201634791

http://www.amazon.com/Network-Management-Principles-Mani-Subramanian/dp/0201357429

http://www.ciscopress.com/bookstore/product.asp?isbn=1587201372#

More online

Optical Network Structure and Terminology

Fig B. Optical Network Structure and Terminology

An Optical Network (Fig. B) is formed by one or more Subnetworks connected by network Links, providing end-to-end service to one or more Customers.
Each subnetwork is administered by an Element Management System (EMS) and the network is administered by a Service provider. A Customer is an entity to which the service provider provides network services.

Element Management System (EMS) represents the abstraction of the subnetworks managed by EMS and the EMS itself.

Subnetwork (Fig. B) is a collection of one or more optical Network Elements (NE),
interconnected by subnetwork links, with connectivity between any pair of NE(s) (i.e., the topology is a connected graph).

A Managed Element (ME) represents the EMS view of the Network Element(NE).

Physical Termination Point (PTP) or Port is an an access point on an NE to which a link or a customer access link is attached. It is the representation of a physical port. It is defined as a source and/or sink for data transport. A good way to think about it is as a hop or (virtual) interface on a network connection. One physical TP can consist of multiple logical TPs. For instance one for each distinguishable data flow.

Connection Termination Point (CTP) represents the actual or potential endpoint of a cross-connection, link connection, or circuit. A CTP is contained within a PTP. In some cases, there is a single CTP associated with a PTP, such as with a E1 PTP. There could also be multiple CTPs, such as with vc12/VC2/VC2/VC4 CTPs contained within an STM-4 PTP. The containment relationship between ME, PTP and CTP is shown in Fig. C.

Fig C. ME - PTP - CTP Relationship

A Topological Link (TL) (Fig.B)  is a  physical link (for example, a fiber) between two PTPs (for example, ports), which are called aEnd TP and zEnd TP of the TL. A topological link starts in a source TP (aEnd) and ends in a sink TP (zEnd).  It represents a topological relationship between two physical termination points (PTPs) for a particular layer rate. The possible set of layer rates are determined by the layer rates terminated by the PTP. The Layer rate (capacity) of TL is determined by the lowest common layer rate of the two end point TPs.  Circuits/Services/Trails are provisioned through links.

A  End points  of a TL may belong to different subnetworks, in which case it is called a “top-level TL”,  or to the same Subnetwork, and then the TL is called  an “inner TL” as shown in Fig. A.

This technical report serves as a short introduction to the terminology and concepts behind practical optical network management. It defines terminology like EMS, ME, PTP, CTP, Subnetwork, Subnetwork connection, Topological Link, PGP, Equipment, Equipment Holder, Route, Cross-Connect etc.. This report is written based on practical experience and various articles/documents available on the web.

Information Modeling

Network Management Systems (NMS) depends on a network database, in which the physical network is represented in an operational way. It enables the programs to exchange information about the network and to keep track of changes in configuration and capacity of the network. For this purpose, an appropriate model of the network is necessary.

Fig. A. Information Modeling

Fig. A shows the creation of an abstract representation of the physical network elements. Individual components in the abstract representation are called functional elements, like NE, PTP, CTP, SNC etc. The mapping of network elements to  functional elements is called information modeling.  For better understanding of optical networks, MTNM information modeling is taken as reference. The terms like EMS, ME, PTP, CTP, Subnetwork, Subnetwork connection, Topological Link, PGP, Equipment, Equipment Holder, Route, Cross-connect are directly taken from well defined MTNM information modeling.

Optical Network Management Concepts -2>>>

One of the most important issues involved with the optical network is network management. Some of the important issues and features are briefly discussed in this section.

Optical network management is done by using multiple layers (EMS, NMS) of management as shown below.

Layered NMS

EMS (Element Management System) manages a subnetwork of the network elements. It typically provided by a network element supplier and capable of managing multiple network elements of that supplier. An EMS may communicate with one or more NE(s)    on an individual or collective basis (e.g., individually to a switch or collectively to SDH ring).

NMS (Network Management System) is responsible for end-to-end  management of a network composed of network elements from multiple suppliers. Instead of directly managing network elements, it relies upon the capabilities of the EMS(s). An NMS may interface with one  or more Service Management Systems and may include some service  management functionality. An NMS may also include some element management layer capabilities that allow it to manage individual NE(s) or it may contain only network management layer functionality to manage one or more EMS(s). NMS talks to the EMSs to get the overall view of the network.

Metro network: is a network that aggregates customer traffic and connects customers to services. The metro network is responsible for receiving network traffic from long-haul transport networks and routing this traffic to and from enterprises and end users.

A good optical network management software system should have
the following features.

• Integrated Network management for SDH, DWDM and optical technologies
• Optical network inventory discovery & reconciliation
• Fault management , Root Cause Analysis (RCA) & Service Impact Analysis(SIA)
• Performance Management
• End-to-end path provisioning (automatic, semi-automatic and manual routing)
• Network restoration \& protection options
• Northbound interfaces (Corba , MTOSI, OSS/J, etc ) to service management and inter-domain management systems}
• Point-and-click operation
• Centralized and secure user administration
• Simple to use Graphical User Interface (GUI)
• High availability and redundancy options

Optical Network Management Concepts -1>>>

the service given by them.  As my laptop is under warranty peroid, they replaced

the monitor frame. They took only two days to fix the issue.