速方日志审计系统

posted @ 2014-12-18 17:41 afunms 阅读(210) | 评论 (0) | 编辑收藏

中国移动WLAN业务PORTAL协议规范

用java实现中国移动WLAN业务PORTAL协议规范

有需要代码的可联系本人。
QQ:316909543

posted @ 2014-11-13 22:30 afunms 阅读(416) | 评论 (0) | 编辑收藏

IT资源监管系统ES

广州速方软件IT资源监管系统ElementSentry
V5.8，提供免费下载试用。
http://www.soofound.com/biz/product/es/intro.htm
QQ:316909543
Email:afunms@soofound.com

posted @ 2013-08-30 13:54 afunms 阅读(316) | 评论 (0) | 编辑收藏

硬件监控--磁盘阵列

通过SNMP实现对磁盘阵列的监控

posted @ 2012-07-24 20:49 afunms 阅读(365) | 评论 (0) | 编辑收藏

SNMP Message Format – SNMP PDU Format

Simple Network Management Protocol i.e. SNMP is a simple request/response protocol in which SNMP manager communicates with SNMP agents/managed devices using SNMP PDU’s (Packet Data Unit). These PDUs are encapsulated in SNMP Messages. An snmp message consists of a sequence that contains SNMP version, Community String, and SNMP PDU and an SNMP PDU forms the body of the message. Look here to read about seven types of SNMP PDUs.

We need to understand that SNMP Message is different from SNMP PDU and hence their formats. Let us now understand SNMP Message Format and SNMP PDUD Format for SNMPv1, SNMPv2 and SNMPv3.

SNMPv1 Message Format

SNMP Version – It is an Integer that identifies the version of SNMP. For SNMPv1, it is 0.
Community String – An Octet String that may contain a string used to add security to SNMP devices.
SNMP PDU – The SNMP PDU (Protocol Data Unit) is used for communication between the SNMP entities.

SNMPv1 PDU Format

For SNMPv1, there are two pdu formats, one for Trap and other for rest of the pdu types.

Below PDU format is applicable for Get, GetNext, Set and Response PDUs:

PDU Type – Specifies the type of PDU
Request ID – Associates SNMP requests with responses.
Error status – Indicates one of a number of errors and error types. It is set only in Response PDU, for rest it is set as 0.
Error index – Associates an error with a particular object instance. It is set only in Response PDU, for rest it is set as 0.
Variable bindings – Each variable binding associates a particular object instance with its current value. For Get and GetNext requests, the value is ignored.

Below PDU format is applicable for Trap PDU:

PDU Type – Specifies the type of PDU as Trap
Enterprise – Identifies the management enterprise under whose registration authority the trap was defined.
Agent address – IP address of the agent
Generic trap type – Used to identiy the generic trap. There are six types of generic traps.
Specific trap type – Used to identify a specific trap.
Time Stamp – Value of the sysUpTime mib object

SNMPv2 Message Format

SNMP Version – It is an Integer that identifies the version of SNMP. For SNMPv2, it is 1.
Community String – An Octet String that may contain a string used to add security to SNMP devices.
SNMP PDU – The SNMP PDU (Protocol Data Unit) is used for communication between the SNMP entities.

SNMPv2 PDU Format

For SNMPv2, there are two pdu formats, one for GetBulk and other for rest of the pdu types.

Below PDU format is applicable for Get, GetNext, Set, Response, Trap and Inform PDUs:

PDU Type- Specifies the type of PDU
Request ID- Associates SNMP requests with responses.
Error Status- Indicates one of a number of errors and error types. It is set only in Response PDU, for rest it is set as 0.
Error Index- Associates an error with a particular object instance. It is set only in Response PDU, for rest it is set as 0.
Variable Bindings- Each variable binding associates a particular object instance with its current value. For Get and GetNext requests, the value is ignored.

Below PDU format is applicable for GetBulk PDU:

PDU Type – Specifies the type of PDU as GetBulk
Request ID- Associates SNMP requests with responses.
Non repeaters- Specifies the number of object instances in the variable bindings field that should be retrieved no more than once from the beginning of the request.
Max repetitions- Defines the maximum number of times that other variables beyond those specified by the Non repeaters field should be retrieved.
Variable Bindings- Each variable binding associates a particular object instance with its current value.

SNMPv3 Message Format

SNMPv3 message format is very different from the above two because of lot of security parameters introduced in this version. Below is how it looks like:

Version – It is an Integer that identifies the version of SNMP. For SNMPv3, it is 3.
ID – This field contains the SNMP message identifier which is a unique ID associated with the message. The msgID field is different from the reqID field available in the PDU.
Max Size – This field represents the maximum size of message which the requesting SNMP entity can accept.
Flags – This field contains the message security level. 0 – message is authenticated, 1 – message uses privacy, 2 – a report PDU is expected for the message
Security Model – This field indicates the security model used to generate the message. When USM is used, it has a value of 3
Engine ID – This field has the SNMPEngineID of the authoritative SNMP entity involved in the transaction. When a request PDU is generated from an SNMP engine, the remote peer (agent for Get request and manager for Trap request) is the authoritative SNMP entity.
Engine Boots – This field has the snmpEngineBoots value of the authoritative SNMP entity involved in the transaction
Engine Time – This field has the snmpEngineTime value of the authoritative SNMP entity involved in the transaction
User Name – This field contains the principal who originated the request.
Security Parameters – This field contains the security parameters that are security model dependent. It contains the authentication parameters and the privacy parameters for USM.
Context Engine ID – Within an administrative domain, the contextEngineID uniquely identifies an SNMP entity that may realize an instance of a context with a particular contextName.
Context Name – A contextName is used to name a context. Each contextName must be unique within an SNMP entity.
PDU – The SNMP PDU (Protocol Data Unit) is used for communication between the SNMP entities.

SNMPv3 PDU Format

The PDU types for SNMPv3 are the same as the SNMPv2.

Thus, above are the message and pdu formats for SNMPv1, SNMPv2 and SNMPv3. Hope you find the information presented here useful. Feel free to leave your footprints for any queries, feedback or suggestions in the comments section below.

posted @ 2012-05-04 16:12 afunms 阅读(779) | 评论 (0) | 编辑收藏

snmp4j FAQ

Why is SNMP4J free?
Currently there is a lack of an affordable well object
oriented designed SNMP implementation for Java. SNMP4J tries to fill this gap.
It is free to get the best support and feedback from the Internet community. In
addition it is a small compensation for the help we got from other open source
projects.
Nevertheless you are welcome to support the development of SNMP4J
by purchasing commercial e-mail support.
Where can I find examples for SNMP4J API usage?
Simple examples are provided by
the JavaDoc of the SNMP class which can be viewed here.
A (nearly) complete example for the SNMP4J API usage
is the console tool. It can be found in the org.snmp4j.tools.console.SnmpRequest
class.
Is SNMP4J thread-safe?
Yes, SNMP4J is designed for multi-threaded
environments. Nevertheless, objects put into a PDU must not be modified while
the corresponding SNMP request is being processed.
Why do I get sometimes a time-out (response == null) on a request although I see log
messages like “Received response that cannot be matched to any outstanding
request...”?
The response of the agent has been received after the
request had been timed out. To solve this, increase the time-out value for the
target.
Why am I always getting a time-out (response == null) when sending a request?
Probably you have forgotten to call the listen() method of the
TransportMapping (once) or the Snmp class before sending the
request.
Can I use a single Snmp instance to request data from multiple SNMP agents at the same time?
Yes, of course! You can either use asynchronous requests and
collect their responses in a one or more callback listeners or you can use
synchronous requests that are send from several threads concurrently.
Can SNMP4J be used with Java EE?
Yes, the SNMP4JSettings class provides the
option to replace the default thread and timer factories by custom ones that use
Java EE resources instead of Java SE threads (timers).

posted @ 2012-05-03 16:09 afunms 阅读(380) | 评论 (0) | 编辑收藏

Difference between SNMPv1 and SNMPv2

Difference between SNMPv1 and SNMPv2

SNMP aka Simple
Network Management Protocol is a simple request/response protocol. Network
manager aka SNMP manager issues a request and managed device aka

SNMP agent returns
the response. This request/response behavior is implemented using protocol
operations and information between manager and agent is transferred using
SNMP PDUs (Packet Data Unit).

SNMPv1 is the
initial implementation of the protocol and SNMPv2 is an enhancement over
version 1. The significant differences between SNMPv1 and SNMPv2 are as below:

•Protocol operations used in SNMPv1 are Get,
GetNext, Set and Trap. SNMPv2 defines two more protocol options GetBulk and
Inform.

•Trap PDU format is different than other
PDU’s formats in SNMPv1. In version 2, trap pdu format is same as the format of
get and set pdu’s.

•In SNMPv1, if in a get request one of the
object instance in multiple-attribute request does not exist or is invalid, no
response would be given, only an error message would return. In SNMPv2, in such
a scenario, response would return for all other object instances or attributes except
the invalid value i.e. partial response would be there rather than error.

To know about the difference in implementation of security in SNMP version 1 & 2, please refer this link.

posted @ 2012-05-02 15:46 afunms 阅读(294) | 评论 (0) | 编辑收藏

Difference Between SNMP Trap and SNMP Notification

Difference Between SNMP Trap and SNMP Notification

We always try to clarify the differences between terminologies that otherwise seem to be similar. In our previous posts, we provided clarification on difference between trap and alarm & difference between trap and inform. As the title suggests, this post talks about difference between SNMP trap and SNMP notification.

If you refer to the SNMP PDU Formats for SNMPv1 and SNMPv2 here, you will realize that SNMPv1 has two different pdu formats, one for trap and another for all remaining snmp operations (get, set etc.). However, in SNMPv2 the pdu format for trap and all other snmp operations (except getbulk) is identical. To standardize the PDU Format of SNMPv1 traps, concept of Notification was introduced in SNMPv2 and same was carried forward to SNMPv3.

Thus, asynchronous event sent to manager by agent is known as Trap in SNMPv1 and Notification in SNMPv2 and SNMPv3.

With respect to the MIB definitions and PDU formats, below are the significant difference between Trap and Notification:
•The macro used for setting trap in SNMPv1 is TRAP-TYPE MACRO and the macro used for setting notifications in SNMPv2/v3 is NOTIFICATION-TYPE MACRO.
•Trap PDU contains agent address whereas Notification PDU contains error status and error index.
•TRAP PDU contains information about generic and specific traps whereas Notification PDU contains Trap OID.
•TRAP is asynchronous. Notification is asynchronous too but SNMV2/SNMPv3 supports confirmed notification known as Inform.

With reference to RFC2576, if a MIB module is changed to conform to the SMIv2, then each occurrence of the TRAP-TYPE macro MUST be changed to a corresponding invocation of the NOTIFICATION-TYPE macro. Have a look at RFC2576 here for translation rules and further clarification on traps and notifications.

Hope you find the information presented here useful. Feel free to leave your inputs in the comments section below.

posted @ 2012-05-01 15:31 afunms 阅读(387) | 评论 (0) | 编辑收藏

java ldap (1)

先用ldapbrowser测试下AD服务器，保证AD是可用的。
以下是java代码：

package com.coreware.ems;

import java.util.Hashtable;

import javax.naming.Context;

import javax.naming.NamingEnumeration;

import javax.naming.NamingException;

import javax.naming.directory.*;

public class SimpleLDAPClient {

public static void main(String[] args) {

Hashtable env = new Hashtable();

env.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.jndi.ldap.LdapCtxFactory");

env.put(Context.PROVIDER_URL, "ldap://192.168.80.130:389/dc=coreware,dc=com");

env.put(Context.SECURITY_AUTHENTICATION, "simple");

env.put(Context.SECURITY_PRINCIPAL, "cn=wangfm,cn=Users,dc=coreware,dc=com");

env.put(Context.SECURITY_CREDENTIALS, "abc123!@#");

DirContext ctx = null;

NamingEnumeration results = null;

try {

ctx = new InitialDirContext(env);

SearchControls controls = new SearchControls();

controls.setSearchScope(SearchControls.SUBTREE_SCOPE);

results = ctx.search("", "(objectclass=person)", controls);

while (results.hasMoreElements()) {

SearchResult searchResult = (SearchResult) results.next();

Attributes attributes = searchResult.getAttributes();

Attribute attr = attributes.get("cn");

String cn = (String) attr.get();

System.out.println(" Person Common Name = " + cn);

}

} catch (NamingException e) {

e.printStackTrace();

} finally {

if (results != null) {

try {

results.close();

} catch (Exception e) {

}

if (ctx != null) {

try {

ctx.close();

} catch (Exception e) {

}

运行结果：
Person Common Name = Administrator
Person Common Name = Guest
Person Common Name = afunms
Person Common Name = db2admin
Person Common Name = AFUNMS-WIN2008
Person Common Name = krbtgt
Person Common Name = wangfm

posted @ 2012-02-23 15:38 afunms 阅读(305) | 评论 (0) | 编辑收藏

spring3 json ajax

spring3---json
在applicationContext.xml中加入

<util:list id="beanList">

</util:list>

</property>

</bean>

<bean id="mappingJacksonHttpMessageConverter"

class="org.springframework.http.converter.json.MappingJacksonHttpMessageConverter" />

这样在action方法加返回bean或map，spring3会把它处理成json格式。如：

@Controller

public class JsonTestController {

@RequestMapping("/getJsonList")

@ResponseBody

public List<ItemTest> searchItemsList()

{

ItemTest item = new ItemTest();

item.setItemnum("123");

item.setItemDesc("123desc");

ItemTest item1 = new ItemTest();

item1.setItemnum("456");

item1.setItemDesc("456desc");

List<ItemTest> list = new ArrayList<ItemTest>();

list.add(item);

list.add(item1);

return list;

}

访问getJsonList.do返回的就是json形式的数据，注意要加上 @ResponseBody

================================================

spring3---ajax---json
网上搜索到一般都是这样：

$(function(){

$("#doImport").click(

function(){

var importInfo = $("#importInfo").serializeObject();

$.ajax({

url:"${base}cmb/doImport.do",

contentType :"application/json",

cache:false,

type:"POST",

data:JSON.stringify(importInfo),

dataType:"json",

success: function(data){

$('#result').val(data.message)

alert(data.message);

},

error:function(){

alert("失败");

}

});

我觉得这个方法写得太复杂了，于是改了它：

function doImport(){

$.ajaxSetup({ cache:false });

var data = {excelFileName:$("#excelFileName").val(),

sheetName:$("#sheetName").val(),

tableName:$("#tableName").val(),

startRow:$("#startRow").val(),

startCol:$("#startCol").val()};

$.getJSON("${base}cmb/doImport.do",data,function(form){

$("#result").val(form.message);

alert(form.message); });

}

action:

@RequestMapping("/cmb/doImport.do")

public @ResponseBody Map<String,String> doImport(HttpServletRequest request, ModelMap model){

System.out.println("===doImport===>>" + DateUtil.getCurrentDateTime());

String excelFileName = request.getParameter("excelFileName");

String sheetName = request.getParameter("sheetName");

String tableName = request.getParameter("tableName");

int startRow = Integer.parseInt(request.getParameter("startRow"));

int startCol = Integer.parseInt(request.getParameter("startCol"));

System.out.println("excelFileName=" + excelFileName);

System.out.println("sheetName=" + sheetName);

System.out.println("tableName="+tableName);

System.out.println("startRow="+startRow);

System.out.println("startCol="+startCol);

Map<String,String> result = new HashMap<String,String>();

result.put("message", "导入成功!");

return result;

}

注意以下几点：
1. ajax必须清缓存：$.ajaxSetup({ cache:false });

2. 将表单的数据组成json格式：
var data = {excelFileName:$("#excelFileName").val(),
       sheetName:$("#sheetName").val(),
       tableName:$("#tableName").val(),
       startRow:$("#startRow").val(),
       startCol:$("#startCol").val()};
# XX与表单组件中的ID对应，如
<input type="hidden" id="excelFileName" value="${excelFileName}" />

3.表单上必须有一个地方能存放返回值：
<input type="hidden" id="message" />
action中的返回值为json格式，
$("#result").val(form.message) 这句话将返回值中的result属性取出赋给表单中的message

posted @ 2011-10-31 10:29 afunms 阅读(936) | 评论 (0) | 编辑收藏

用apache.poi读excel

public static void main(String[] args) throws Exception {

POIFSFileSystem pfs = new POIFSFileSystem(new FileInputStream("D:\\test_xls.xls"));

HSSFWorkbook hwk = new HSSFWorkbook(pfs);

HSSFSheet sheet = hwk.getSheet("Sheet1");

try{

int lrn = sheet.getLastRowNum();

for(int r = 0;r<lrn;r++){

Row row = sheet.getRow(r);

int lcn = row.getLastCellNum();

for(int c = 0;c<lcn;c++){

if(row.getCell(c)==null)

System.out.println("R=" + r + ",C=" + c + ":NULL");

else

System.out.println("R=" + r + ",C=" + c + ":" + row.getCell(c).toString());

}

}catch(Exception e){

e.printStackTrace();

}

posted @ 2011-10-09 16:53 afunms 阅读(237) | 评论 (0) | 编辑收藏

portal demo

1、新建web工程testportal，向工程中添加portal2.0 jar包

2、创建portlet

package com.miiwill;

import java.io.IOException;

import javax.portlet.GenericPortlet;

import javax.portlet.PortletException;

import javax.portlet.RenderRequest;

import javax.portlet.RenderResponse;

public class Helloworld extends GenericPortlet {

@Override

protected void doView(RenderRequest request, RenderResponse response)

throws PortletException, IOException {

response.setContentType("text/html");

response.getWriter().println("<h2>hello world,View Mode</h2>");

}

@Override

protected void doEdit(RenderRequest request, RenderResponse response)

throws PortletException, IOException {

response.setContentType("text/html");

response.getWriter().println("<h2>hello world,Edit Mode</h2>");

}

3、修改web.xml

<?xml version="1.0" encoding="UTF-8"?>

<web-app version="2.5" xmlns="http://java.sun.com/xml/ns/javaee"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="http://java.sun.com/xml/ns/javaee

http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">

<servlet-name>HelloWorldPortal</servlet-name>

<servlet-class>org.apache.pluto.container.driver.PortletServlet</servlet-class>

<init-param>

<param-name>portlet-name</param-name>

<param-value>HelloWorldPortalDemo</param-value>

</init-param>

<init-param>

<param-name>portlet-guid</param-name>

<param-value>HelloWorldPortal.HelloWorldPortalDemo</param-value>

</init-param>

<init-param>

<param-name>portlet-class</param-name>

<param-value>com.miiwill.Helloworld</param-value>

</init-param>

<!--PortletServlet执行init时，根据charset参数获取字符集，

然后在执行响应时调用response.setContentType来设置编码-->

<init-param>

<param-name>charset</param-name>

<param-value>utf-8</param-value>

</init-param>

<load-on-startup>1</load-on-startup>

</servlet>

<servlet-mapping>

<servlet-name>HelloWorldPortal</servlet-name>

<url-pattern>/PlutoInvoker/*</url-pattern>

</servlet-mapping>

<welcome-file-list>

<welcome-file>index.jsp</welcome-file>

</welcome-file-list>

</web-app>

4、创建portlet.xml

<?xml version="1.0" encoding="UTF-8"?>

<portlet-app

xmlns="http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd"

version="2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd

http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd">

<description>My First Portal Demo</description>

<portlet-name>HelloWorldPortalDemo</portlet-name>

<display-name>HelloWorld Portal Demo</display-name>

<portlet-class>com.miiwill.Helloworld</portlet-class>

<expiration-cache>-1</expiration-cache>

<mime-type>text/html</mime-type>

<portlet-mode>VIEW</portlet-mode>

<portlet-mode>EDIT</portlet-mode>

</supports>

<portlet-info>

<title>My First Portal Demo : HelloWorldPortal</title>

</portlet-info>

</portlet>

</portlet-app>

5、部署portal

将WebRoot copy到webapps下，改名为testportal。

注意将WEB-INF\lib中的2 个jar删除，因为pluto的lib中已经有了。不删除会有冲突！

1）启动pluto,http://localhost:8080/pluto/

以pluto/pluto登录。

2）创建一个页

3）注册portlet

4）测试portlet

posted @ 2011-09-30 09:07 afunms 阅读(596) | 评论 (0) | 编辑收藏

pluto安装

从apache网上下载pluto-2.0.3-bundle.zip
解压后，修改bin\startup.bat，配置上jdk
set JAVA_HOME=../../jdk1.6.0_03

然后启动pluto，发现有错。查看日志
Caused by: java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/E:/nms4/pluto/webapps/pluto/WEB-INF/lib/jaxb-impl-2.1.9.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/)
at com.sun.xml.bind.v2.model.impl.ModelBuilder.<clinit>(ModelBuilder.java:173)
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:432)
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:297)
at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:139)
at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:117)
at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:188)

估计是jaxb造成的，于是将webapps\pluto\WEB-INF\lib下的jaxb-impl-2.1.9.jar删除。
再启动pluto，成功！

posted @ 2011-09-28 10:06 afunms 阅读(462) | 评论 (0) | 编辑收藏

第一次接触IPMI

下载ipmiutil-2.7.8-win32，不用安装直接能用。
只可惜还没有开源或免费的java包来支持ipmi。

在dell服务器上测试
C:\ipmiutil>ipmiutil   health
ipmiutil ver 2.78
ihealth ver 2.78
BMC version      = 1.55, IPMI v2.0
BMC manufacturer = 0002a2 (Dell), product = 0100
BIOS Version     = 1.2.2
IPMI driver type = 10        (ms)
Chassis Status   = 21 00 00 (on, restore=last_state, last_pwr=)
Power State      = 2a       (unknown)
Selftest status = 0055     (OK)
Power On Hours   = 0 hours (0 days)
get_chan_auth error: ret = c1
ipmiutil health, Invalid Command

C:\ipmiutil>ipmiutil sensor
ipmiutil ver 2.78
isensor: version 2.78
-- BMC version 1.55, IPMI version 2.0
supports device sdrs
_ID_ SDR_Type_xx ET Own Typ S_Num   Sens_Description   Hex & Interp Reading
0001 SDR Full 01 01 20 a 01 snum 01 CPU 1 Temp       = 59 OK   -39.00 degrees C
0002 SDR Full 01 01 20 a 01 snum 02 CPU 2 Temp       = 56 OK   -42.00 degrees C
0003 SDR Full 01 01 20 a 01 snum 03 CPU 3 Temp       = 56 OK   -42.00 degrees C
0004 SDR Full 01 01 20 a 01 snum 04 CPU 4 Temp       = 56 OK   -42.00 degrees C
0005 SDR Full 01 01 20 a 01 snum 05 PS 1 Temp        = 00 Init 0.00 degrees C
0006 SDR Full 01 01 20 a 01 snum 06 PS 2 Temp        = 00 Init 0.00 degrees C
0007 SDR Full 01 01 20 a 01 snum 07 PS 3 Temp        = a6 OK   38.00 degrees C
0008 SDR Full 01 01 20 a 01 snum 08 PS 4 Temp        = a3 OK   35.00 degrees C
0009 SDR Full 01 01 20 a 01 snum 09 IOR Temp         = 9d OK   29.00 degrees C
000a SDR Full 01 01 20 a 01 snum 0c IOH 1 Temp       = ab Warn-hi 43.00 degrees
C
000b SDR Full 01 01 20 a 01 snum 0d IOH 2 Temp       = b0 Crit-hi 48.00 degrees
C
000c SDR Full 01 01 20 a 01 snum 0e Ambient Temp     = 99 OK   25.00 degrees C
000d SDR Full 01 01 20 a 01 snum 0f Planar Temp      = a1 OK   33.00 degrees C
000e SDR Full 01 01 20 a 01 snum b0 DIMM Bank A      = 9d OK   29.00 degrees C
000f SDR Full 01 01 20 a 01 snum b1 DIMM Bank B      = 00 Init 0.00 degrees C
0010 SDR Full 01 01 20 a 01 snum b2 DIMM Bank C      = 9c OK   28.00 degrees C
0011 SDR Full 01 01 20 a 01 snum b3 DIMM Bank D      = 00 Init 0.00 degrees C
0012 SDR Full 01 01 20 a 01 snum b4 DIMM Bank E      = 9c OK   28.00 degrees C
0013 SDR Full 01 01 20 a 01 snum b5 DIMM Bank F      = 00 Init 0.00 degrees C
0014 SDR Full 01 01 20 a 01 snum b6 DIMM Bank G      = 9c OK   28.00 degrees C
0015 SDR Full 01 01 20 a 01 snum b7 DIMM Bank H      = 00 Init 0.00 degrees C
0016 SDR Comp 02 6f 20 a 29 snum 10 CMOS Battery     = 0000 OK
0017 SDR Comp 02 6f 20 a 29 snum 11 ROMB Battery     = 0000 OK
0018 SDR Comp 02 03 20 a 02 snum 12 VCORE PG         = 0001 Crit-hi
0019 SDR Comp 02 03 20 a 02 snum 13 VCORE PG         = 0001 Crit-hi
001a SDR Comp 02 03 20 a 02 snum 14 VCORE            = 0001 Crit-hi
001b SDR Comp 02 03 20 a 02 snum 15 VCORE            = 0001 Crit-hi
001c SDR Comp 02 03 20 a 02 snum 16 VCACHE PG        = 0001 Crit-hi
001d SDR Comp 02 03 20 a 02 snum 17 VCACHE PG        = 0001 Crit-hi
001e SDR Comp 02 03 20 a 02 snum 18 VCACHE           = 0001 Crit-hi
001f SDR Comp 02 03 20 a 02 snum 19 VCACHE           = 0001 Crit-hi
0020 SDR Comp 02 03 20 a 02 snum 1a VIO PG           = 0001 Crit-hi
0021 SDR Comp 02 03 20 a 02 snum 1b VIO PG           = 0001 Crit-hi
0022 SDR Comp 02 03 20 a 02 snum 1c CPU 1.8 PLL PG   = 0001 Crit-hi
0023 SDR Comp 02 03 20 a 02 snum 1d 8V Rear PG       = 0001 Crit-hi
0024 SDR Comp 02 03 20 a 02 snum 1e 8V Front PG      = 0001 Crit-hi
0025 SDR Comp 02 03 20 a 02 snum 1f 5V Rear PG       = 0001 Crit-hi
0026 SDR Comp 02 03 20 a 02 snum 20 5V Front PG      = 0001 Crit-hi
0027 SDR Comp 02 03 20 a 02 snum 21 3.3V PG          = 0001 Crit-hi
0028 SDR Comp 02 03 20 a 02 snum 22 1.8V PG          = 0001 Crit-hi
0029 SDR Comp 02 03 20 a 02 snum 23 1.5V PG          = 0001 Crit-hi
002a SDR Comp 02 03 20 a 02 snum 24 1.1V PG          = 0001 Crit-hi
002b SDR Comp 02 03 20 a 02 snum 25 0.9V PG          = 0001 Crit-hi
002c SDR Comp 02 03 20 a 02 snum 26 Mem VR PG        = 0001 Crit-hi
002d SDR Comp 02 03 20 a 02 snum 27 Mem VR PG        = 0001 Crit-hi
002e SDR Comp 02 03 20 a 02 snum 28 Mem VR PG        = 0001 Crit-hi
002f SDR Comp 02 03 20 a 02 snum 29 Mem VR PG        = 0001 Crit-hi
0030 SDR Comp 02 03 20 a 02 snum 2a Mem VR PG        = 0001 Crit-hi
0031 SDR Comp 02 03 20 a 02 snum 2b Mem VR PG        = 0001 Crit-hi
0032 SDR Comp 02 03 20 a 02 snum 2c Mem VR PG        = 0001 Crit-hi
0033 SDR Comp 02 03 20 a 02 snum 2d Mem VR PG        = 0001 Crit-hi
0034 SDR Comp 02 03 20 a 02 snum 2f VR PG            = 0001 Crit-hi
0035 SDR Comp 02 03 20 a 02 snum 2e VR1 PG           = 0001 Crit-hi
0036 SDR Comp 02 03 20 a 02 snum a0 VR2 PG           = 0001 Crit-hi
0037 SDR Comp 02 03 20 a 01 snum a1 IOH1 THERMTRIP   = 0000 OK
0038 SDR Comp 02 03 20 a 01 snum a2 IOH2 THERMTRIP   = 0000 OK
0039 SDR Comp 02 03 20 a 02 snum 5f PFault Fail Safe = 0000 Unknown
003a SDR Comp 02 6f 20 a 25 snum 5d Heatsink Pres    = 0001 OK*
003b SDR Comp 02 6f 20 a 25 snum 70 iDRAC6 Ent Pres = 0001 OK*
003c SDR Comp 02 6f 20 a 25 snum 59 USB Cable Pres   = 0001 OK*
003d SDR Comp 02 6f 20 a 25 snum 5a Stor Adapt Pres = 0001 OK*
003e SDR Comp 02 6f 20 a 25 snum 5b PCIe Riser Pres = 0002 Present
003f SDR Comp 02 6f 20 a 25 snum 5c IO Riser Pres    = 0000 NotAvailable
0040 SDR Full 01 01 20 a 04 snum 30 FAN 1 RPM        = 1b OK   3240.00 RPM
0041 SDR Full 01 01 20 a 04 snum 31 FAN 2 RPM        = 1b OK   3240.00 RPM
0042 SDR Full 01 01 20 a 04 snum 32 FAN 3 RPM        = 00 Crit-lo 0.00 RPM
0043 SDR Full 01 01 20 a 04 snum 33 FAN 4 RPM        = 1d OK   3480.00 RPM
0044 SDR Full 01 01 20 a 04 snum 34 FAN 5 RPM        = 1d OK   3480.00 RPM
0045 SDR Full 01 01 20 a 04 snum 35 FAN 6 RPM        = 1d OK   3480.00 RPM
0046 SDR Full 01 01 20 a 04 snum 36 Fan RPM          = 00 OK   0.00 RPM
0047 SDR Full 01 01 20 a 04 snum 37 Fan RPM          = 00 OK   0.00 RPM
0048 SDR Full 01 01 20 a 04 snum 38 Fan RPM          = 10 OK   1920.00 RPM
0049 SDR Full 01 01 20 a 04 snum 39 Fan RPM          = 11 OK   2040.00 RPM
004a SDR Comp 02 6f 20 a 25 snum 50 Presence         = 0001 OK*
004b SDR Comp 02 6f 20 a 25 snum 51 Presence         = 0001 OK*
004c SDR Comp 02 6f 20 a 25 snum 52 Presence         = 0001 OK*
004d SDR Comp 02 6f 20 a 25 snum 53 Presence         = 0001 OK*
004e SDR Comp 02 6f 20 a 25 snum 54 Presence         = 0001 OK*
004f SDR Comp 02 6f 20 a 25 snum 55 Presence         = 0001 OK*
0050 SDR Comp 02 6f 20 a 25 snum 56 Presence         = 0001 OK*
0051 SDR Comp 02 6f 20 a 25 snum 57 Presence         = 0001 OK*
0052 SDR Comp 02 6f 20 a 25 snum 58 Presence         = 0001 OK*
0053 SDR Comp 02 6f 20 a 07 snum 60 Status           = 0080 ProcPresent
0054 SDR Comp 02 6f 20 a 07 snum 61 Status           = 0080 ProcPresent
0055 SDR Comp 02 6f 20 a 07 snum 62 Status           = 0080 ProcPresent
0056 SDR Comp 02 6f 20 a 07 snum 63 Status           = 0080 ProcPresent
0057 SDR Comp 02 6f 20 a 08 snum 64 Status           = 0009 AC_Lost
0058 SDR Comp 02 6f 20 a 08 snum 65 Status           = 0009 AC_Lost
0059 SDR Comp 02 6f 20 a 08 snum 66 Status           = 0001 Present
005a SDR Comp 02 6f 20 a 08 snum 67 Status           = 0001 Present
005b SDR Full 01 01 20 a 03 snum 94 Current          = 00 Unknown 0.00 Requested
sensor, data, or record not present
005c SDR Full 01 01 20 a 03 snum 95 Current          = 00 Unknown 0.00 Requested
sensor, data, or record not present
005d SDR Full 01 01 20 a 03 snum 9a Current          = 20 OK   1.28 Amps
005e SDR Full 01 01 20 a 03 snum 9b Current          = 1e OK   1.20 Amps
005f SDR Full 01 01 20 a 02 snum 96 Voltage          = 00 Unknown 0.00 Requested
sensor, data, or record not present
0060 SDR Full 01 01 20 a 02 snum 97 Voltage          = 00 Unknown 0.00 Requested
sensor, data, or record not present
0061 SDR Full 01 01 20 a 02 snum 9c Voltage          = 61 OK   194.00 Volts
0062 SDR Full 01 01 20 a 02 snum 9d Voltage          = 61 OK   194.00 Volts
0063 SDR Comp 02 6f 20 a 1b snum 68 Riser Config     = 0001 _
0064 SDR Comp 02 6f 20 a 23 snum 71 OS Watchdog      = 0000 OK
0065 SDR Comp 02 6f 20 a 10 snum 72 SEL              = 0000 Unknown
0066 SDR Comp 02 6f 20 a 05 snum 73 Intrusion        = 0001 ChassisIntrus
0067 SDR Comp 02 0b 20 a 08 snum 74 PS Redundancy    = 0040 NotAvailable
0068 SDR Comp 02 0b 20 a 04 snum 75 Fan Redundancy   = 0002 RedunLost
0069 SDR Full 01 01 20 a 03 snum 98 System Level     = 2e OK   460.00 Watts
006a SDR Comp 02 6f 20 a c0 snum 99 Power Optimized = 0001 Enabled
006b SDR Comp 02 6f 20 a 0d snum 80 Drive            = 0001 Absent
006c SDR Comp 02 6f 20 a 0d snum 8f Drive 15         = 0000 Unused
006d SDR Comp 02 6f 20 a 1b snum 90 Cable SAS A      = 0001 _
006e SDR Comp 02 6f 20 a 1b snum 91 Cable SAS B      = 0001 _
006f SDR Comp 02 70 20 a 15 snum d0 SD1 Status       = 0000 _
0070 SDR Comp 02 70 20 a 15 snum d1 SD2 Status       = 0000 _
0071 SDR Comp 02 0b 20 a 15 snum d2 SD Redundancy    = 0001 _
0072 SDR Comp 02 70 20 a 15 snum d3 VFlash Media     = 0000 _
0073 SDR Full 01 01 20 a 01 snum b8 Mem Rsr A Temp   = 9f OK   31.00 degrees C
0074 SDR Full 01 01 20 a 01 snum b9 Mem Rsr B Temp   = 00 Init 0.00 degrees C
0075 SDR Full 01 01 20 a 01 snum ba Mem Rsr C Temp   = 9f OK   31.00 degrees C
0076 SDR Full 01 01 20 a 01 snum bb Mem Rsr D Temp   = 00 Init 0.00 degrees C
0077 SDR Full 01 01 20 a 01 snum bc Mem Rsr E Temp   = 9e OK   30.00 degrees C
0078 SDR Full 01 01 20 a 01 snum bd Mem Rsr F Temp   = 00 Init 0.00 degrees C
0079 SDR Full 01 01 20 a 01 snum be Mem Rsr G Temp   = 9f OK   31.00 degrees C
007a SDR Full 01 01 20 a 01 snum bf Mem Rsr H Temp   = 00 Init 0.00 degrees C
007b SDR Full 01 01 20 a 01 snum c0 MB A-A Temp      = 98 OK   24.00 degrees C
007c SDR Full 01 01 20 a 01 snum c1 MB A-B Temp      = 99 OK   25.00 degrees C
007d SDR Full 01 01 20 a 01 snum c2 MB B-A Temp      = 00 Init 0.00 degrees C
007e SDR Full 01 01 20 a 01 snum c3 MB B-B Temp      = 00 Init 0.00 degrees C
007f SDR Full 01 01 20 a 01 snum c4 MB C-A Temp      = 96 OK   22.00 degrees C
0080 SDR Full 01 01 20 a 01 snum c5 MB C-B Temp      = 98 OK   24.00 degrees C
0081 SDR Full 01 01 20 a 01 snum c6 MB D-A Temp      = 00 Init 0.00 degrees C
0082 SDR Full 01 01 20 a 01 snum c7 MB D-B Temp      = 00 Init 0.00 degrees C
0083 SDR Full 01 01 20 a 01 snum c8 MB E-A Temp      = 93 OK   19.00 degrees C
0084 SDR Full 01 01 20 a 01 snum c9 MB E-B Temp      = 98 OK   24.00 degrees C
0085 SDR Full 01 01 20 a 01 snum ca MB F-A Temp      = 00 Init 0.00 degrees C
0086 SDR Full 01 01 20 a 01 snum cb MB F-B Temp      = 00 Init 0.00 degrees C
0087 SDR Full 01 01 20 a 01 snum cc MB G-A Temp      = 98 OK   24.00 degrees C
0088 SDR Full 01 01 20 a 01 snum cd MB G-B Temp      = 98 OK   24.00 degrees C
0089 SDR Full 01 01 20 a 01 snum ce MB H-A Temp      = 00 Init 0.00 degrees C
008a SDR Full 01 01 20 a 01 snum cf MB H-B Temp      = 00 Init 0.00 degrees C
008b SDR Comp 02 03 20 a 02 snum a3 10G Power        = 0001 Crit-hi
008c SDR Comp 02 01 20 a 01 snum ab VCORE Temp       = 0000 Unknown
008d SDR Comp 02 01 20 a 01 snum ac VCACHE Temp      = 0000 Unknown
008e SDR Comp 02 01 20 a 01 snum ad Mem VR Temp      = 0000 Unknown
008f SDR Comp 02 03 20 a 01 snum ae Critical Cooling = 0000 Unknown
0090 SDR Comp 02 03 20 a 02 snum af Sys Pwr Draw     = 0000 Unknown
0091 SDR IPMB 12 11 dev: 20 00 df 07 01 iDRAC6
0092 SDR FRU 11 17 dev: 20 00 80 00 07 01 System Board
0093 SDR FRU 11 0f dev: 20 b0 02 00 03 01 CPU1
0094 SDR FRU 11 0f dev: 20 b0 02 00 03 02 CPU2
0095 SDR FRU 11 0f dev: 20 b0 02 00 03 03 CPU3
0096 SDR FRU 11 0f dev: 20 b0 02 00 03 04 CPU4
0097 SDR FRU 11 0f dev: 20 02 80 00 0a 01 PS 1
0098 SDR FRU 11 0f dev: 20 03 80 00 0a 02 PS 2
0099 SDR FRU 11 0f dev: 20 04 80 00 0a 03 PS 3
009a SDR FRU 11 0f dev: 20 05 80 00 0a 04 PS 4
009b SDR FRU 11 12 dev: 20 06 80 00 1a 03 Storage
009c SDR FRU 11 12 dev: 20 07 80 00 1a 01 Storage
009d SDR FRU 11 13 dev: 20 08 02 00 10 01 IO Riser
009e SDR FRU 11 16 dev: 20 09 02 00 08 01 Mem Riser A
009f SDR FRU 11 16 dev: 20 0a 02 00 08 02 Mem Riser B
00a0 SDR FRU 11 16 dev: 20 0b 02 00 08 03 Mem Riser C
00a1 SDR FRU 11 16 dev: 20 0c 02 00 08 04 Mem Riser D
00a2 SDR FRU 11 16 dev: 20 0d 02 00 08 05 Mem Riser E
00a3 SDR FRU 11 16 dev: 20 0e 02 00 08 06 Mem Riser F
00a4 SDR FRU 11 16 dev: 20 0f 02 00 08 07 Mem Riser G
00a5 SDR FRU 11 16 dev: 20 10 02 00 08 08 Mem Riser H
00a6 SDR FRU 11 15 dev: 20 b0 02 00 10 02 PCIe Riser
00a7 SDR FRU 11 0b dev: 20 b0 02 00 0b 01
00a8 SDR FRU 11 0b dev: 20 b0 02 00 0b 02
00a9 SDR Comp 02 6f b1 a 0c snum 01 ECC Corr Err     = 0000 Unknown
00aa SDR Comp 02 6f b1 a 0c snum 02 ECC Uncorr Err   = 0000 Unknown
00ab SDR Comp 02 6f b1 a 13 snum 03 I/O Channel Chk = 0000 Unknown
00ac SDR Comp 02 6f b1 a 13 snum 04 PCI Parity Err   = 0000 Unknown
00ad SDR Comp 02 6f b1 a 13 snum 05 PCI System Err   = 0000 Unknown
00ae SDR Comp 02 6f b1 a 10 snum 06 SBE Log Disabled = 0000 Unknown
00af SDR Comp 02 6f b1 a 10 snum 07 Logging Disabled = 0000 Unknown
00b0 SDR Comp 02 6f b1 a 12 snum 08 Unknown          = 0000 Unknown
00b1 SDR Comp 02 07 b1 a 07 snum 0a CPU Protocol Err = 0000 Unknown
00b2 SDR Comp 02 07 b1 a 07 snum 0b CPU Bus PERR     = 0000 Unknown
00b3 SDR Comp 02 07 b1 a 07 snum 0c CPU Init Err     = 0000 Unknown
00b4 SDR Comp 02 07 b1 a 07 snum 0d CPU Machine Chk = 0000 Unknown
00b5 SDR Comp 02 0b b1 a 0c snum 11 Memory Spared    = 0000 Unknown
00b6 SDR Comp 02 0b b1 a 0c snum 12 Memory Mirrored = 0000 Unknown
00b7 SDR Comp 02 0b b1 a 0c snum 13 Memory RAID      = 0000 Unknown
00b8 SDR Comp 02 6f b1 a 0c snum 14 Memory Added     = 0000 Unknown
00b9 SDR Comp 02 6f b1 a 0c snum 15 Memory Removed   = 0000 Unknown
00ba SDR Comp 02 6f b1 a 0c snum 16 Memory Cfg Err   = 0000 Unknown
00bb SDR Comp 02 0b b1 a 0c snum 17 Mem Redun Gain   = 0000 Unknown
00bc SDR Comp 02 6f b1 a 13 snum 18 PCIE Fatal Err   = 0000 Unknown
00bd SDR Comp 02 6f b1 a 13 snum 19 Chipset Err      = 0000 Unknown
00be SDR Comp 02 7e b1 a c1 snum 1a Err Reg Pointer = 0000 Unknown
00bf SDR Comp 02 07 b1 a 0c snum 1b Mem ECC Warning = 0000 Unknown
00c0 SDR Comp 02 07 b1 a 0c snum 1c Mem CRC Err      = 0000 Unknown
00c1 SDR Comp 02 07 b1 a 0c snum 1d USB Over-current = 0000 Unknown
00c2 SDR Comp 02 6f b1 a 0f snum 1e POST Err         = 0000 Unknown
00c3 SDR Comp 02 6f b1 a 2b snum 1f Hdwr version err = 0000 Unknown
00c4 SDR Comp 02 6f b1 a 0c snum 20 Mem Overtemp     = 0000 Unknown
00c5 SDR Comp 02 6f b1 a 0c snum 21 Mem Fatal SB CRC = 0000 Unknown
00c6 SDR Comp 02 6f b1 a 0c snum 22 Mem Fatal NB CRC = 0000 Unknown
00c7 SDR Comp 02 6f b1 a 11 snum 23 OS Watchdog Time = 0000 Unknown
00c8 SDR Comp 02 6f b1 a c2 snum 26 Non Fatal PCI Er = 0000 Unknown
00c9 SDR Comp 02 6f b1 a c3 snum 27 Fatal IO Error   = 0000 Unknown
00ca SDR Comp 02 6f b1 a c1 snum 28 MSR Info Log     = 0000 Unknown
00cb SDR Comp 02 6f b1 a c2 snum 29 Non Fatal QPI Er = 0000 Unknown
00cc SDR Comp 02 6f b1 a c8 snum 30 QPIRC Warning    = 0000 Unknown
00cd SDR Comp 02 6f b1 a c8 snum 31 MRC Non Fatal Er = 0000 Unknown
00ce SDR Comp 02 6f b1 a c8 snum 32 MRC SMI LFO      = 0000 Unknown
00cf SDR Comp 02 6f b1 a c8 snum 33 MRC Warning      = 0000 Unknown
00d0 SDR EntA 08 10 07 01 c0: 03 01 03 04 0a 01 0a 04
00d1 SDR EntA 08 10 07 01 c0: 10 01 10 02 08 01 08 08
00d2 SDR EntA 08 10 10 01 c0: 0b 01 0b 02 00 00 00 00
ipmiutil sensor, completed successfully

posted @ 2011-09-08 09:17 afunms 阅读(1251) | 评论 (0) | 编辑收藏

在Tomcat中集成jotm

1.下载ow2-jotm-dist-2.2.1

2.把jotm所有的jar放到Tomcat/lib下

3.创建文件carol.properties

# # JNDI (Protocol Invocation)
carol.protocols=jrmp

# Local RMI Invocation
carol.jvm.rmi.local.call=true

# do not use CAROL JNDI wrapper
carol.start.jndi=false

# do not start a name server
carol.start.ns=false

# Naming Factory
carol.jndi.java.nameing.factory.url.pkgs=org.apache.nameing

4.修改数据源配置文件
<?xml version='1.0' encoding='utf-8'?>
<Context path="/xflow" debug="0" reloadable="false" docBase="D:\workspace\xflow\WebRoot\">
   <Resource name="jdbc/afunms"
        auth="Container"
        type="javax.sql.DataSource"
        factory="org.objectweb.jotm.datasource.DataSourceFactory"
        driverClassName="com.mysql.jdbc.Driver"
        username="root"
  password="root"
  url="jdbc:mysql://localhost:3306/netflow?useUnicode=true&characterEncoding=utf-8" />
<Resource name="UserTransaction"
            auth="Container"
            type="javax.transaction.UserTransaction" />
<Transaction factory="org.objectweb.jotm.UserTransactionFactory"
               jotm.timeout="60" />
</Context>

5.java代码这样写：
Context ctx = new InitialContext();
DataSource ds = (DataSource)ctx.lookup("java:comp/env/jdbc/afunms");
UserTransaction ut = (UserTransaction)ctx.lookup("java:comp/UserTransaction");

posted @ 2011-08-29 16:38 afunms 阅读(618) | 评论 (0) | 编辑收藏

研究portal的实现

研究Java来实现Portal。

1) Dynamic Include
首先，我们采用最简单的思路，我们用100个JSP文件(1.jsp, 2.jsp, 3.jsp, … 100.jsp等)，代表100个Portlet。
用户页面MyPage.jsp包含用户选定的多个Portlet。
现在，假设用户选取的Portlet为1.jsp, 3.jsp, 7.jsp等3个Portlet，那么我们如何在MyPage.jsp中显示这些Portlet？最直观的做法是，用jsp:include。比如：
<table>
<tr><td>
<jsp:include page=”1.jsp” />
</td></tr>
<tr><td>
<jsp:include page=”3.jsp” />
</td></tr>
<tr><td>
<jsp:include page=”7.jsp” />
</td></tr>
</table>
由于<jsp:include>只能指定固定的jsp文件名，不能动态指定jsp文件名。我们需要把<jsp:include>翻译为Java code – RequestDispatcher.include();
下面我们换成这种写法。
Java代码
<table>
<tr><td>
<% request.getRequestDispatcher(”1.jsp”).include(request, response); />
</td></tr>
<tr><td>
<% request.getRequestDispatcher(”3.jsp”).include(request, response); />
</td></tr>
<tr><td>
<% request.getRequestDispatcher(”7.jsp”).include(request, response); />
</td></tr>
</table>

进一步改进MyPage.jsp。
Java代码
<% String[] fileNames = {“1.jsp”, “3.jsp”, “7.jsp”}; %>
<table>
<% for(int i = 0; i < fileNames.length; i++) {
String fileName = fileName s[i]; %>
<tr><td>
<% request.getRequestDispatcher(fileName).include(request, response); />
</td></tr>
<% } // end for %>
</table>

其中的fileNames的内容可以各种各样，只要RequestDispatcher能够处理。
比如Velocity，fileNames = {“1.vm”, “3.vm”, “7.vm”};
比如URL，fileNames = {“/portlet1.do”, “/portlet3.do”, “/portlet4.do”};
我们可以看到，如果我们从用户配置中读取fileNames的内容，这就是一个简单的Portal实现。
Java代码
<% String[] fileNames = (String[])session.getAttribute(“portlets.config”); %>
<table>
<% for(int i = 0; i < fileNames.length; i++) {
String fileName = fileNames[i]; %>
<tr><td>
<% request.getRequestDispatcher(fileName).include(request, response); />
</td></tr>
<% } // end for %>
</table>

2) Portlet Interface
下面我们来扩展这个例子。
假设每个Portlet都规定实现一个Portlet接口。
Java代码
interface Portlet {
void render(request, response);
};

MyPage.jsp如下：

<% String[] portletClassNames = (String[])session.getAttribute(“portlets.config”); %>
<table>
<% for(int i = 0; i < portletClassNames.length; i++) {
String className = portletClassNames[i];
Portlet portlet = (Portlet)Class.forName(className).newInstance(); %>
<tr><td>
<% portlet. render (request, response); />
</td></tr>
<% } // end for %>
</table>

Portlet类的示例代码如下：
public class Portlet7{
public void render(request, response){
    request.getRequestDispatcher(“7.jsp”).include(request, response);
}
};

interface Portlet {
void render(request, response);
};

MyPage.jsp如下：

<% String[] portletClassNames = (String[])session.getAttribute(“portlets.config”); %>
<table>
<% for(int i = 0; i < portletClassNames.length; i++) {
String className = portletClassNames[i];
Portlet portlet = (Portlet)Class.forName(className).newInstance(); %>
<tr><td>
<% portlet. render (request, response); />
</td></tr>
<% } // end for %>
</table>

Portlet类的示例代码如下：
public class Portlet7{
public void render(request, response){
request.getRequestDispatcher(“7.jsp”).include(request, response);
}
};

上述代码是Portal显示Portlet的核心流程的一个简化版本。
JSR168 Portlet规范里面定义了真正的Portlet接口定义。

posted @ 2011-08-28 12:29 afunms 阅读(201) | 评论 (0) | 编辑收藏

揭阳topo

去年在揭阳痛苦了三天三夜也没把拓扑做出来，今天有机会再次在同一环境下测试程序。
与去年相比，产品的成熟度有较大提高。我也基本搞清楚H3C各型号FDB数据的获取方法。

拓扑发现结果
	开始时间	结束时间	耗时
1	2011-07-15 16:01:33	2011-07-15 16:08:03	6分钟30秒

发现设备
	IP地址	名称	型号	类型
1	10.46.129.100	jygaj7510E	hh3c-s7510E	路由交换机
2	10.46.129.111	jygaj4507	cat4507	路由交换机
3	10.46.131.146	JieXiDaDui	hh3c-s5500-28C-EI	路由交换机
4	10.46.159.51	JYSJ_5500	hh3c-s5500-28C-EI	路由交换机
5	10.46.131.150	HuiLaiDaDui	hh3c-s5500-28C-EI	路由交换机
6	10.46.131.138	YuHuDaDui	hh3c-s5500-28C-EI	路由交换机
7	10.46.131.193	HuiLaiGaoSuDaDui	hh3c-s5500-28C-EI	路由交换机
8	10.46.131.169	RongChengDaDui	hh3c-s5500-28C-EI	路由交换机
9	10.46.131.190	JiaoJingZhiDui	hh3c-S7503E-S	路由交换机
10	10.46.131.158	JieDongGaoSuDaDui	hh3c-s5500-28C-EI	路由交换机
11	10.46.131.1	DongShanDaDui	hh3c-s5500-28C-EI	路由交换机
12	10.46.131.202	PuHuiGaoSuDaDui	hh3c-s5500-28C-EI	路由交换机
13	10.46.131.118	PuHuiGaoSu2Donggang	hh3c-s5100-24P-SI	路由交换机
14	10.46.131.166	GuiLingKaoChang	hh3c-s5100-24P-SI	路由交换机
15	10.46.130.128	jiedong	hh3c-S7503E-S	路由交换机
16	10.46.131.10	RongXinZhongDui	hh3c-s5100-24P-SI	路由交换机
17	10.46.131.170	JinXianZhongDui	hh3c-s5100-24P-SI	路由交换机
18	10.46.150.96	puning	hh3c-S7503E-S	路由交换机
19	10.46.155.160	huilai	s3328	交换机
20	10.46.157.65	rongcheng	hh3c-s5500-28C-EI	路由交换机
21	10.46.155.130	AoJiang	hh3c-S5120-28P-SI	路由交换机
22	10.46.155.178	KuiFeng	hh3c-S5120-28P-SI	路由交换机
23	10.46.155.226	ZhouTian	hh3c-S5120-28P-SI	路由交换机
24	10.46.155.242	DongLong	hh3c-S5120-28P-SI	路由交换机
25	10.46.156.82	HeLin	hh3c-S5120-28P-SI	路由交换机
26	10.46.155.62	XianKanShouSuo	hh3c-S5120-28P-SI	路由交换机
27	10.46.131.6	YuQiaoZhongDui	s2326TP	路由交换机
28	10.46.136.18	jiexi	hh3c-S7503E-S	路由交换机
29	10.46.131.126	PuHuiGaosu_1_zd_xichang	hh3c-s5100-24P-SI	路由交换机
30	10.46.135.249	jygaj3560A	catalyst3560G24TS	交换机
31	10.46.129.226	jieyang_3640	cisco3640	路由交换机
32	10.46.159.100	puhua	hh3c-s5100-24P-EI	路由交换机
33	10.46.159.40	dananshan	hh3c-s5100-24P-EI	路由交换机
34	10.46.155.210	10.46.155.210	hh3c-S5120-28P-SI	路由交换机
35	10.46.141.64	yuhu	hh3c-s5500-28C-EI	路由交换机
36	10.46.133.64	dongshan-master	hh3c-s5500-28C-EI	路由交换机
37	10.46.149.30	shuishangpaichusuo	hh3c-s5100-24P-EI	路由交换机
38	10.46.146.99	jingxiao	hh3c-s5500-28C-EI	路由交换机
39	10.46.135.44	kanshousuo	hh3c-s5100-24P-EI	路由交换机
40	10.46.135.8	tejing	hh3c-s5100-24P-EI	路由交换机
合计:40台

发现子网
	子网地址	子网掩码
1	10.46.128.0	255.255.224.0
2	10.46.128.112	255.255.255.248
3	10.46.128.120	255.255.255.248
4	10.46.128.128	255.255.255.248
5	10.46.128.136	255.255.255.248
6	10.46.128.16	255.255.255.248
7	10.46.128.160	255.255.255.248
8	10.46.128.176	255.255.255.248
9	10.46.128.184	255.255.255.248
10	10.46.128.192	255.255.255.248
11	10.46.128.200	255.255.255.248
12	10.46.128.208	255.255.255.240
13	10.46.128.224	255.255.255.248
14	10.46.128.232	255.255.255.248
15	10.46.128.248	255.255.255.248
16	10.46.128.8	255.255.255.248
17	10.46.129.0	255.255.255.0
18	10.46.130.0	255.255.255.0
19	10.46.131.0	255.255.255.252
20	10.46.131.100	255.255.255.252
21	10.46.131.116	255.255.255.252
22	10.46.131.12	255.255.255.252
23	10.46.131.124	255.255.255.252
24	10.46.131.128	255.255.255.252
25	10.46.131.136	255.255.255.252
26	10.46.131.140	255.255.255.252
27	10.46.131.144	255.255.255.252
28	10.46.131.148	255.255.255.252
29	10.46.131.156	255.255.255.252
30	10.46.131.164	255.255.255.252
31	10.46.131.168	255.255.255.252
32	10.46.131.172	255.255.255.252
33	10.46.131.176	255.255.255.252
34	10.46.131.180	255.255.255.252
35	10.46.131.188	255.255.255.252
36	10.46.131.192	255.255.255.252
37	10.46.131.196	255.255.255.252
38	10.46.131.200	255.255.255.252
39	10.46.131.240	255.255.255.252
40	10.46.131.244	255.255.255.252
41	10.46.131.248	255.255.255.248
42	10.46.131.4	255.255.255.252
43	10.46.131.8	255.255.255.252
44	10.46.131.80	255.255.255.252
45	10.46.131.88	255.255.255.252
46	10.46.131.92	255.255.255.252
47	10.46.131.96	255.255.255.252
48	10.46.132.0	255.255.255.0
49	10.46.133.0	255.255.255.0
50	10.46.134.0	255.255.255.0
51	10.46.135.0	255.255.255.0
52	10.46.135.128	255.255.255.128
53	10.46.135.32	255.255.255.224
54	10.46.135.64	255.255.255.192
55	10.46.136.0	255.255.255.252
56	10.46.136.100	255.255.255.252
57	10.46.136.108	255.255.255.252
58	10.46.136.136	255.255.255.252
59	10.46.136.16	255.255.255.252
60	10.46.136.20	255.255.255.252
61	10.46.136.200	255.255.255.252
62	10.46.136.32	255.255.255.252
63	10.46.137.0	255.255.255.0
64	10.46.138.0	255.255.255.0
65	10.46.139.0	255.255.255.224
66	10.46.139.128	255.255.255.224
67	10.46.139.192	255.255.255.240
68	10.46.139.232	255.255.255.248
69	10.46.139.240	255.255.255.240
70	10.46.139.32	255.255.255.224
71	10.46.139.64	255.255.255.192
72	10.46.140.0	255.255.255.0
73	10.46.141.0	255.255.255.128
74	10.46.141.128	255.255.255.128
75	10.46.142.0	255.255.255.240
76	10.46.142.128	255.255.255.224
77	10.46.142.16	255.255.255.240
78	10.46.142.160	255.255.255.224
79	10.46.142.192	255.255.255.224
80	10.46.142.224	255.255.255.224
81	10.46.142.32	255.255.255.240
82	10.46.142.64	255.255.255.192
83	10.46.143.0	255.255.255.192
84	10.46.143.128	255.255.255.224
85	10.46.143.160	255.255.255.224
86	10.46.143.192	255.255.255.192
87	10.46.143.64	255.255.255.224
88	10.46.143.96	255.255.255.224
89	10.46.144.0	255.255.255.224
90	10.46.144.112	255.255.255.240
91	10.46.144.128	255.255.255.240
92	10.46.144.144	255.255.255.240
93	10.46.144.160	255.255.255.240
94	10.46.144.176	255.255.255.240
95	10.46.144.224	255.255.255.240
96	10.46.144.240	255.255.255.240
97	10.46.144.64	255.255.255.224
98	10.46.144.96	255.255.255.240
99	10.46.145.0	255.255.255.240
100	10.46.145.128	255.255.255.240
101	10.46.145.144	255.255.255.240
102	10.46.145.16	255.255.255.240
103	10.46.145.160	255.255.255.240
104	10.46.145.176	255.255.255.240
105	10.46.145.192	255.255.255.240
106	10.46.145.208	255.255.255.240
107	10.46.145.224	255.255.255.240
108	10.46.145.32	255.255.255.240
109	10.46.145.48	255.255.255.240
110	10.46.145.64	255.255.255.240
111	10.46.145.80	255.255.255.240
112	10.46.145.96	255.255.255.240
113	10.46.146.0	255.255.255.0
114	10.46.147.0	255.255.255.0
合计:114个

发现链路
	名称
1	jygaj7510E[GigabitEthernet0/0/28]--JieXiDaDui[GigabitEthernet1/0/24]
2	jygaj7510E[GigabitEthernet0/0/24]--JiaoJingZhiDui[GigabitEthernet1/0/39]
3	JiaoJingZhiDui[GigabitEthernet1/0/6]--DongShanDaDui[GigabitEthernet1/0/21]
4	jygaj7510E[GigabitEthernet0/0/26]--JieDongGaoSuDaDui[GigabitEthernet1/0/24]
5	jygaj7510E[GigabitEthernet0/0/30]--RongChengDaDui[GigabitEthernet1/0/24]
6	jygaj7510E[GigabitEthernet0/0/27]--HuiLaiDaDui[GigabitEthernet1/0/24]
7	jygaj7510E[GigabitEthernet0/0/39]--JYSJ_5500[GigabitEthernet1/0/1]
8	jygaj7510E[GigabitEthernet0/0/29]--YuHuDaDui[GigabitEthernet1/0/24]
9	jygaj7510E[GigabitEthernet0/0/25]--HuiLaiGaoSuDaDui[GigabitEthernet1/0/24]
10	jygaj7510E[GigabitEthernet0/0/40]--jygaj4507[GigabitEthernet3/32]
11	jygaj4507[GigabitEthernet3/26]--jieyang_3640[FastEthernet2/0]
12	jygaj7510E[GigabitEthernet0/0/6]--rongcheng[GigabitEthernet1/0/24]
13	jygaj7510E[GigabitEthernet0/0/32]--PuHuiGaoSuDaDui[GigabitEthernet1/0/24]
14	jygaj7510E[GigabitEthernet0/0/4]--jiexi[GigabitEthernet1/0/24]
15	jygaj7510E[GigabitEthernet0/0/7]--yuhu[GigabitEthernet1/0/24]
16	jygaj7510E[GigabitEthernet0/0/5]--dongshan-master[GigabitEthernet1/0/24]
17	jygaj7510E[GigabitEthernet0/0/3]--puning[GigabitEthernet1/0/40]
18	jygaj7510E[GigabitEthernet0/0/1]--jiedong[GigabitEthernet1/0/24]
19	jygaj7510E[GigabitEthernet0/0/13]--jingxiao[GigabitEthernet1/0/24]
20	DongShanDaDui[GigabitEthernet1/0/23]--YuQiaoZhongDui[Vlanif3]
21	huilai[Ethernet0/0/8]--HeLin[GigabitEthernet1/0/24]
22	JYSJ_5500[GigabitEthernet1/0/6]--shuishangpaichusuo[GigabitEthernet1/0/24]
23	JYSJ_5500[GigabitEthernet1/0/3]--puhua[GigabitEthernet1/0/24]
24	JYSJ_5500[GigabitEthernet1/0/5]--tejing[GigabitEthernet1/0/24]
25	RongChengDaDui[GigabitEthernet1/0/22]--RongXinZhongDui[GigabitEthernet1/0/24]
26	JYSJ_5500[GigabitEthernet1/0/2]--dananshan[GigabitEthernet1/0/24]
27	JYSJ_5500[GigabitEthernet1/0/4]--kanshousuo[GigabitEthernet1/0/24]
28	huilai[Ethernet0/0/7]--DongLong[GigabitEthernet1/0/24]
29	huilai[Ethernet0/0/5]--KuiFeng[GigabitEthernet1/0/20]
30	RongChengDaDui[GigabitEthernet1/0/21]--JinXianZhongDui[GigabitEthernet1/0/24]
31	huilai[Ethernet0/0/2]--ZhouTian[GigabitEthernet1/0/24]
32	huilai[Ethernet0/0/3]--10.46.155.210[GigabitEthernet1/0/24]
33	huilai[Ethernet0/0/6]--AoJiang[GigabitEthernet1/0/24]
34	huilai[Ethernet0/0/1]--XianKanShouSuo[GigabitEthernet1/0/24]
35	JiaoJingZhiDui[GigabitEthernet1/0/40]--GuiLingKaoChang[GigabitEthernet1/0/24]
36	jygaj7510E[GigabitEthernet0/0/48]--jygaj3560A[GigabitEthernet0/27]
37	jygaj7510E[GigabitEthernet0/0/2]--huilai[Ethernet0/0/24]
38	JiaoJingZhiDui[GigabitEthernet1/0/8]--PuHuiGaoSu2Donggang[GigabitEthernet1/0/2]
39	JiaoJingZhiDui[GigabitEthernet1/0/7]--PuHuiGaosu_1_zd_xichang[GigabitEthernet1/0/24]
40	jygaj4507[GigabitEthernet3/21]--jygaj3560A[GigabitEthernet0/22]
合计:40条

posted @ 2011-07-15 22:53 afunms 阅读(432) | 评论 (1) | 编辑收藏

JBPM流程展现改进

1.在连线加上文字
2.换了图标

posted @ 2011-05-30 10:52 afunms 阅读(182) | 评论 (0) | 编辑收藏

JBPM流程展现

摘要: Flex开发的JBPM流程展现器 ---JBPM流程定义XML---- Code highlighting produced by Actipro CodeHighlighter (freeware)http://www.CodeHighlighter.com/--><?xml version="1.0" encoding="UTF-8"?><proces... 阅读全文

posted @ 2011-05-28 17:07 afunms 阅读(364) | 评论 (0) | 编辑收藏

2.INTRODUCTION TOIT SERVICE MANAGEMENT

IT Service Management Objectives
ITIL is a Best Practice Framework used …..
1.To align IT services with the current and future needs
   of the business and its Customers
2.To develop the quality of the IT services delivered
3.To reduce the long term cost of service provision

Why Service Management
1.Increasing IT visibility and Reliance
2.Increasing demand from Business to deliver effective
   IT solutions/services (Cost Effective)
3.Increasing complexity of IT infrastructure and processes
4.Increasing competition
5.Increasing pressure to realise return on investment

Considerations
1.Do not be over ambitious
2.Consider what elements already exist, are in use and effective
3.Identify what can be re-used or needs to be developed
4.Adapt the guidelines to meet your requirements

Process Improvement Model
Process Improvement Stages
1.Process improvement definition
2.Communication
3.Planning
4.Implementation
5.Review and Audit

ITIL Service Management
Service Support
   Day to day operational support of IT services
Service Delivery
   Long term planning and improvement of IT service provision

Key Definitions
Customer: recipient of a service: usually the Customer management
                 has responsibility for the funding of the service.
Provider: the unit responsible for the provision of IT service.
Supplier: a third party responsible for supplying or supporting
               underpinning elements of the IT service.
User: the person using the service on a daily basis.

IT Service Management Overview

posted @ 2011-05-02 09:37 afunms 阅读(180) | 评论 (0) | 编辑收藏

1.Introduction

ITIL Service Management Foundation

Course Objectives

1.To introduce ITIL As Best Practice framework
Terms, Definitions, Phrases
2.Gain an understanding of the essential ITIL processes and how they relate
to each other,in order to support and deliver a quality IT service

Course Content – Day 1
1.Introduction
2.Introduction to IT Service Management
3.Service Desk
4.Configuration Management
5.Incident Management
6.Problem Management
7.Change Management
8.Release Management

Course Content – Day 2
1.Service Level Management
2.Financial Management for IT Services
3.Capacity Management
4.IT Service Continuity Management
5.Availability Management

ITIL Overview
1.ITIL is a Best Practice Framework
2.Integrated into OGC and BSI guidance
3.ITIL Philosophy – Scaleable Process driven approach
4.Key Objective 1
5.Align IT services with the Current and Future needs of the business and its Customers
6.Key Objective 2
7.To improve Quality of the services delivered
8.Key Objective 3
9.Reduce long term Cost of service provision

Introduction to Service Management
The Service Desk
Configuration Management
Incident Management
Problem Management
Change Management
Release Management

posted @ 2011-05-01 09:11 afunms 阅读(155) | 评论 (0) | 编辑收藏

Tomcat服务器IP冲突

启动Tomcat后，服务器IP冲突或IP地址改变会导致以下错误：

I/O exception (java.net.ConnectException)

caught when processing request: Connection timed out: connect

Retrying request

posted @ 2011-02-24 13:57 afunms 阅读(288) | 评论 (0) | 编辑收藏

正则表达式中转义字符

除 .$ ^ { [ ( | ) * + ? \ 外，其他字符与自身匹配。

点的转义：. ==> \\u002E
美元符号的转义：$ ==> \\u0024
乘方符号的转义：^ ==> \\u005E
左大括号的转义：{ ==> \\u007B
左方括号的转义：[ ==> \\u005B
左圆括号的转义：( ==> \\u0028
竖线的转义：| ==> \\u007C
右圆括号的转义：) ==> \\u0029
星号的转义：* ==> \\u002A
加号的转义：+ ==> \\u002B
问号的转义：? ==> \\u003F
反斜杠的转义：\ ==> \\u005C

test:

public static void main(String[] args){

Pattern p = Pattern.compile("/\\u002A\\s{1,5}\\d{0,4}\\s{1,5}\\u002A/");

Matcher m = p.matcher("/* 1369 */");

System.out.println(m.find());

}

结果为true

posted @ 2011-01-29 09:34 afunms 阅读(3431) | 评论 (0) | 编辑收藏

log4j

转http://dev.csdn.net/htmls/21/21291.html
log4j虽然用了很久，其实一直没搞清楚。今天认真学习了。

1.简介
程序开发环境中的日志记录是由嵌入在程序中以输出一些对开发人员有用信息的语句所组成。例如，跟踪语句（trace），结构转储和常见的System.out.println或printf调试语句。log4j提供分级方法在程序中嵌入日志记录语句。日志信息具有多种输出格式和多个输出级别。

使用一个专门的日志记录包，可以减轻对成千上万的System.out.println语句的维护成本，因为日志记录可以通过配置脚本在运行时得以控制。log4j维护嵌入在程序代码中的日志记录语句。通过规范日志记录的处理过程，一些人认为应该鼓励更多的使用日志记录并且获得更高程度的效率。

2.安装
为了使用我们即将要安装的日志记录工具，还必须要设置操作环境，只有这样，工具才能知道从哪里找到它所需要的信息，并且操作系统知道从哪里找到这个工具。那么，怎样做呢？实际上，它要求更改操作环境。我有一些这方面的资格文档。 Configuring A Windows Working Environment 和 Configuring A Unix Working Environment.

从 http://jakarta.apache.org/log4j/docs/download.html下载log4j发行版。

解压存档文件到合适的目录中。

添加文件 dist/lib/log4j-1.2.6.jar 到 CLASSPATH 环境变量中。

3.log4j的基本概念
使用log4j大概涉及3个主要概念:

公共类 Logger

Logger 负责处理日志记录的大部分操作。

公共接口 Appender

Appender 负责控制日志记录操作的输出。

公共抽象类Layout

Layout 负责格式化Appender的输出。

3.1.Logger
日志记录器(Logger)是日志处理的核心组件。log4j具有5种正常级别(Level)。日志记录器(Logger)的可用级别Level (不包括自定义级别 Level)，以下内容就是摘自log4j API (http://jakarta.apache.org/log4j/docs/api/index.html):

static Level DEBUG

DEBUG Level指出细粒度信息事件对调试应用程序是非常有帮助的。

static Level INFO

INFO level表明消息在粗粒度级别上突出强调应用程序的运行过程。

static Level WARN

WARN level表明会出现潜在错误的情形。

static Level ERROR

ERROR level指出虽然发生错误事件，但仍然不影响系统的继续运行。

static Level FATAL

FATAL level指出每个严重的错误事件将会导致应用程序的退出。

另外，还有两个可用的特别的日志记录级别: (以下描述来自log4j API http://jakarta.apache.org/log4j/docs/api/index.html):

static Level ALL

ALL Level是最低等级的，用于打开所有日志记录。

static Level OFF

OFF Level是最高等级的，用于关闭所有日志记录。

日志记录器（Logger）的行为是分等级的。如下表所示：

图.日志输出等级

日志记录器（Logger）将只输出那些级别高于或等于它的级别的信息。如果没有设置日志记录器（Logger）的级别，那么它将会继承最近的祖先的级别。因此，如果在包com.foo.bar中创建一个日志记录器（Logger）并且没有设置级别，那它将会继承在包com.foo中创建的日志记录器（Logger）的级别。如果在com.foo中没有创建日志记录器（Logger）的话,那么在com.foo.bar中创建的日志记录器（Logger）将继承root 日志记录器（Logger）的级别，root日志记录器（Logger）经常被实例化而可用，它的级别为DEBUG。

有很多方法可以创建一个日志记录器（Logger），下面方法可以取回root日志记录器:

Logger logger = Logger.getRootLogger();

还可以这样创建一个新的日志记录器:

Logger logger = Logger.getLogger("MyLogger");

比较常用的用法，就是根据类名实例化一个静态的全局日志记录器:

static Logger logger = Logger.getLogger(test.class);

所有这些创建的叫"logger"的日志记录器都可以用下面方法设置级别:

logger.setLevel((Level)Level.WARN);

可以使用7个级别中的任何一个; Level.DEBUG, Level.INFO, Level.WARN, Level.ERROR, Level.FATAL, Level.ALL and Level.OFF.

3.2.Appender
Appender 控制日志怎样输出。下面列出一些可用的Appender(log4j API中所描述的 http://jakarta.apache.org/log4j/docs/api/index.html):

ConsoleAppender:使用用户指定的布局(layout) 输出日志事件到System.out或者 System.err。默认的目标是System.out。

DailyRollingFileAppender 扩展FileAppender，因此多个日志文件可以以一个用户选定的频率进行循环日志记录。

FileAppender 把日志事件写入一个文件

RollingFileAppender 扩展FileAppender备份容量达到一定大小的日志文件。

WriterAppender根据用户的选择把日志事件写入到Writer或者OutputStream。

SMTPAppender 当特定的日志事件发生时，一般是指发生错误或者重大错误时，发送一封邮件。

SocketAppender 给远程日志服务器（通常是网络套接字节点）发送日志事件（LoggingEvent）对象。

SocketHubAppender 给远程日志服务器群组（通常是网络套接字节点）发送日志事件（LoggingEvent）对象。

SyslogAppender给远程异步日志记录的后台精灵程序(daemon)发送消息。

TelnetAppender 一个专用于向只读网络套接字发送消息的log4j appender。

还可以实现 Appender 接口，创建以自己的方式进行日志输出的Appender。

3.2.1.使用ConsoleAppender
ConsoleAppender可以用这种方式创建：

ConsoleAppender appender = new ConsoleAppender(new PatternLayout());

创建了一个控制台appender，具有一个默认的PatternLayout。它使用了默认的System.out 输出。

3.2.2.使用FileAppender
FileAppender可以用这种方式创建:

          FileAppender appender = null;
          try {
             appender = new FileAppender(new PatternLayout(),"filename");
          } catch(Exception e) {}

上面用到的构造函数:

FileAppender(Layout layout, String filename)
实例化一个FileAppender并且打开变量"filename"指定的文件。

另一个有用的构造函数是：

FileAppender(Layout layout, String filename, boolean append)
实例化一个FileAppender并且打开变量"filename"指定的文件。

这个构造函数还可以选择是否对指定的文件进行追加的方式输出。如果没有指定值，那么默认的方式就是追加。

3.2.3.使用WriterAppender
WriterAppender可以用这种方式创建:

          WriterAppender appender = null;
          try {
            appender = new WriterAppender(new PatternLayout(),new FileOutputStream("filename"));
          } catch(Exception e) {}

这个WriterAppender使用的构造函数带有PatternLayout和OutputStream参数，在这种情况下， FileOutputStream用于向一个文件输出。当然，它还具有其他可用的构造函数。

3.3.Layout
Appender必须使用一个与之相关联的 Layout，这样它才能知道怎样格式化它的输出。当前，log4j具有三种类型的Layout:

HTMLLayout 格式化日志输出为HTML表格。

PatternLayout 根据指定的转换模式格式化日志输出，或者如果没有指定任何转换模式，就使用默认的转换模式。

SimpleLayout 以一种非常简单的方式格式化日志输出，它打印级别 Level，然后跟着一个破折号“-“ ，最后才是日志消息。

3.4.基本示例
3.4.1.SimpleLayout和 FileAppender
这里是一个非常简单的例子，程序实现了SimpleLayout和FileAppender:

import org.apache.log4j.Level;
import org.apache.log4j.Logger;
import org.apache.log4j.SimpleLayout;
import org.apache.log4j.FileAppender;
public class simpandfile {
   static Logger logger = Logger.getLogger(simpandfile.class);
   public static void main(String args[]) {
      SimpleLayout layout = new SimpleLayout();
      FileAppender appender = null;
      try {
         appender = new FileAppender(layout,"output1.txt",false);
      } catch(Exception e) {}
      logger.addAppender(appender);
      logger.setLevel((Level) Level.DEBUG);
      logger.debug("Here is some DEBUG");
      logger.info("Here is some INFO");
      logger.warn("Here is some WARN");
      logger.error("Here is some ERROR");
      logger.fatal("Here is some FATAL");
   }
}

你可以下载: simpandfile.java。还可以查看它的输出： output1.txt.

3.4.2.HTMLLayout和 WriterAppender
这里是一个非常简单的例子，程序实现了 HTMLLayout和WriterAppender:

import java.io.*;
import org.apache.log4j.Level;
import org.apache.log4j.Logger;
import org.apache.log4j.HTMLLayout;
import org.apache.log4j.WriterAppender;
public class htmlandwrite {
   static Logger logger = Logger.getLogger(htmlandwrite.class);
   public static void main(String args[]) {
      HTMLLayout layout = new HTMLLayout();
      WriterAppender appender = null;
      try {
         FileOutputStream output = new FileOutputStream("output2.html");
         appender = new WriterAppender(layout,output);
      } catch(Exception e) {}
      logger.addAppender(appender);
      logger.setLevel((Level) Level.DEBUG);
      logger.debug("Here is some DEBUG");
      logger.info("Here is some INFO");
      logger.warn("Here is some WARN");
      logger.error("Here is some ERROR");
      logger.fatal("Here is some FATAL");
   }
}

你可以下载: simpandfile.java. 还可以查看它的输出：output1.txt.

3.4.3.PatternLayout和 ConsoleAppender
这里是一个非常简单的例子，程序实现了PatternLayout和ConsoleAppender:

import org.apache.log4j.Level;
import org.apache.log4j.Logger;
import org.apache.log4j.PatternLayout;
import org.apache.log4j.ConsoleAppender;
public class consandpatt {
   static Logger logger = Logger.getLogger(consandpatt.class);
   public static void main(String args[]) {
      // Note, %n is newline
      String pattern = "Milliseconds since program start: %r %n";
             pattern += "Classname of caller: %C %n";
             pattern += "Date in ISO8601 format: %d{ISO8601} %n";
             pattern += "Location of log event: %l %n";
             pattern += "Message: %m %n %n";

      PatternLayout layout = new PatternLayout(pattern);
      ConsoleAppender appender = new ConsoleAppender(layout);
      logger.addAppender(appender);
      logger.setLevel((Level) Level.DEBUG);
      logger.debug("Here is some DEBUG");
      logger.info("Here is some INFO");
      logger.warn("Here is some WARN");
      logger.error("Here is some ERROR");
      logger.fatal("Here is some FATAL");
   }
}

你可以下载:simpandfile.java. 还可以查看它的输出： output2.txt.

4.使用外部配置文件
Log4j经常与外部日志文件联合使用，这样很多可选项不必硬编码在软件中。使用外部配置文件的优点就是修改可选项不需要重新编译程序。唯一的缺点就是，由于用到io 指令，速度稍微有些减慢。

有两个方法可以用来指定外部配置文件：文本文件或者XML文件。既然现在所有事情都写成XML文件，那么该教程就重点讲解XML文件方法，但是也包含相关文本文件的例子。首先，看看下面的XML配置文件示例：

<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
<log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/">

<appender name="ConsoleAppender" class="org.apache.log4j.ConsoleAppender">
    <layout class="org.apache.log4j.SimpleLayout"/>
</appender>
<root>
    <priority value ="debug" />
    <appender-ref ref="ConsoleAppender"/>
</root>
</log4j:configuration>

文件以标准的XML声明作为开始，后面跟着指出DTD（文档类型定义）的DOCTYPE声明，它定义了XML文件的结构，例如，什么元素可以嵌入在其他元素中等等。上面文件在log4j发行版的src/java/org/apache/log4j/xml目录中。接着看看封装所有元素的 log4j:configuration 元素，它在DOCTYPE声明中被指定为根元素。嵌入在根元素中有两个结构：

这里创建一个名叫"ConsoleAppender"的 Appender，注意，你可以选择任何名字，该示例之所以选择"ConsoleAppender"，完全是为了示例的设计。接着这个appender类以全名形式给出，经常用规范（fully qualified）类名。 Appender必须具有一个指定的 name和class。嵌入在 Appender之内的是 layout元素，这里它被指定为SimpleLayout。 Layout 必须具有一个 class属性。

root元素必须存在且不能被子类化。示例中的优先级被设置为"debug"，设置appender饱含一个appender-ref元素。还有更多的属性或元素可以指定。查看log4j发行版中的src/java/org/apache/log4j/xml/log4j.dtd以了解关于XML配置文件结构的更多信息。可以用下面这种方法把配置信息文件读入到Java程序中:

DOMConfigurator.configure("configurationfile.xml");

DOMConfigurator 用一棵DOM树来初始化log4j环境。这里是示例中的XML配置文件：plainlog4jconfig.xml。这里是执行该配置文件的程序: files/externalxmltest.java:

import org.apache.log4j.Logger;
import org.apache.log4j.xml.DOMConfigurator;
public class externalxmltest {
   static Logger logger = Logger.getLogger(filetest.class);
   public static void main(String args[]) {
      DOMConfigurator.configure("xmllog4jconfig.xml");
      logger.debug("Here is some DEBUG");
      logger.info("Here is some INFO");
      logger.warn("Here is some WARN");
      logger.error("Here is some ERROR");
      logger.fatal("Here is some FATAL");
   }
}

这里是一个实现带有PatternLayout的FileAppender的日志记录器Logger的XML配置文件:

<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
<log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/">

<appender name="appender" class="org.apache.log4j.FileAppender">
    <param name="File" value="Indentify-Log.txt"/>
    <param name="Append" value="false"/>
    <layout class="org.apache.log4j.PatternLayout">
      <param name="ConversionPattern" value="%d [%t] %p - %m%n"/>
    </layout>
</appender>
<root>
    <priority value ="debug"/>
    <appender-ref ref="appender"/>
</root>
</log4j:configuration>

你可以从这里下载示例: xmllog4jconfig2.xml。想要得到更多的使用XML文件配置log4j环境的例子，请查看log4j发行版的目录src/java/org/apache/log4j/xml/examples/ 。

这就是上面讨论的文本文件形式的配置文件:

# initialise root logger with level DEBUG and call it BLAH
log4j.rootLogger=DEBUG, BLAH
# add a ConsoleAppender to the logger BLAH
log4j.appender.BLAH=org.apache.log4j.ConsoleAppender
# set set that layout to be SimpleLayout
log4j.appender.BLAH.layout=org.apache.log4j.SimpleLayout

从这里可以下载: plainlog4jconfig.txt。这就是执行该配置文件的程序:

import org.apache.log4j.Logger;
import org.apache.log4j.PropertyConfigurator;
public class externalplaintest {
   static Logger logger = Logger.getLogger(externalplaintest.class);
   public static void main(String args[]) {
      PropertyConfigurator.configure("plainlog4jconfig.xml");
      logger.debug("Here is some DEBUG");
      logger.info("Here is some INFO");
      logger.warn("Here is some WARN");
      logger.error("Here is some ERROR");
      logger.fatal("Here is some FATAL");
   }
}

你可以下载使用该配置文件的示例： externalplaintest.java。想要获得更多的使用文本文件配置log4j环境的例子，请查看log4j发行版中的目录examples。

使用外部配置文件的例子就简单的讨论到这里，现在应该可以肯定你已经有能力独立学习更多的log4j发行版和测试版中提供的例子。

posted @ 2011-01-28 10:14 afunms 阅读(239) | 评论 (0) | 编辑收藏

snmp4j中文乱码问题

snmp4j遇到中文直接转成16进制字符串，网上有些解决办法，试过之后，乱码问题是解决了，却带来意想不到的副作用。
研究之后，还是自己写一个方法，把16进制字符串转成正常的字符串。

/**

* 解决snmp4j中文乱码问题

*/

public static String getChinese(String octetString){

try{

String[] temps = octetString.split(":");

byte[] bs = new byte[temps.length];

for(int i=0;i<temps.length;i++)

bs[i] = (byte)Integer.parseInt(temps[i],16);

return new String(bs,"GB2312");

}catch(Exception e){

return null;

}

posted @ 2011-01-19 09:40 afunms 阅读(1923) | 评论 (1) | 编辑收藏

华为交换机fdb表的四种可能

华为交换机FDB表四种取值方式：

1. bridge.mib

getTable(dot1dTpFdbAddress,dot1dTpFdbPort)

2.q-bridge.mib

getTable(dot1dTpFdbAddress,dot1dTpFdbPort)

3. huawei-l2mam.mib

walk(hwDynFdbPort)

4. huawei-lswmam.mib

posted @ 2010-12-28 12:29 afunms 阅读(2007) | 评论 (1) | 编辑收藏

tomcat把日志输出到文本文件

在Linux系统中，Tomcat 启动后默认将很多信息都写入到catalina.out 文件中，我们可以通过tail -f catalina.out 来跟踪Tomcat 和相关应用运行的情况。在windows下，我们使用startup.bat启动Tomcat以后，会发现catalina日志与Linux记录的内容有很大区别，大多信息只输出到屏幕而没有记录到catalina.out里面。
本文的内容就是要实现在windows下，将相关的控制台输出记录到后台的catalina.out文件中以便将来查看。
关于在Windows2003下如何实现类似Linux下tail命令功能的方法，请见让windows也拥有tail功能一文

把控制台的信息输出到%CATALINA_BASE%\logs\catalina.out里：
一、修改startup.bat中
call "%EXECUTABLE%" start %CMD_LINE_ARGS%
为
call "%EXECUTABLE%" run %CMD_LINE_ARGS%
二、修改catalina.bat中
rem Execute Java with the applicable properties
if not "%JPDA%" == "" goto doJpda
if not "%SECURITY_POLICY_FILE%" == "" goto doSecurity
%_EXECJAVA% %JAVA_OPTS% %CATALINA_OPTS% %DEBUG_OPTS% -Djava.endorsed.dirs="%JAVA_ENDORSED_DIRS%" -classpath "%CLASSPATH%" -Dcatalina.base="%CATALINA_BASE%" -Dcatalina.home="%CATALINA_HOME%" -Djava.io.tmpdir="%CATALINA_TMPDIR%" %MAINCLASS% %CMD_LINE_ARGS% %ACTION%
goto end
:doSecurity
%_EXECJAVA% %JAVA_OPTS% %CATALINA_OPTS% %DEBUG_OPTS% -Djava.endorsed.dirs="%JAVA_ENDORSED_DIRS%" -classpath "%CLASSPATH%" -Djava.security.manager -Djava.security.policy=="%SECURITY_POLICY_FILE%" -Dcatalina.base="%CATALINA_BASE%" -Dcatalina.home="%CATALINA_HOME%" -Djava.io.tmpdir="%CATALINA_TMPDIR%" %MAINCLASS% %CMD_LINE_ARGS% %ACTION%
goto end
:doJpda
if not "%SECURITY_POLICY_FILE%" == "" goto doSecurityJpda
%_EXECJAVA% %JAVA_OPTS% %CATALINA_OPTS% -Xdebug -Xrunjdwp:transport=%JPDA_TRANSPORT%,address=%JPDA_ADDRESS%,server=y,suspend=n %DEBUG_OPTS% -Djava.endorsed.dirs="%JAVA_ENDORSED_DIRS%" -classpath "%CLASSPATH%" -Dcatalina.base="%CATALINA_BASE%" -Dcatalina.home="%CATALINA_HOME%" -Djava.io.tmpdir="%CATALINA_TMPDIR%" %MAINCLASS% %CMD_LINE_ARGS% %ACTION%
goto end
:doSecurityJpda
%_EXECJAVA% %JAVA_OPTS% %CATALINA_OPTS% -Xdebug -Xrunjdwp:transport=%JPDA_TRANSPORT%,address=%JPDA_ADDRESS%,server=y,suspend=n %DEBUG_OPTS% -Djava.endorsed.dirs="%JAVA_ENDORSED_DIRS%" -classpath "%CLASSPATH%" -Djava.security.manager -Djava.security.policy=="%SECURITY_POLICY_FILE%" -Dcatalina.base="%CATALINA_BASE%" -Dcatalina.home="%CATALINA_HOME%" -Djava.io.tmpdir="%CATALINA_TMPDIR%" %MAINCLASS% %CMD_LINE_ARGS% %ACTION%
goto end

为：

rem Execute Java with the applicable properties
if not "%JPDA%" == "" goto doJpda
if not "%SECURITY_POLICY_FILE%" == "" goto doSecurity
%_EXECJAVA% %JAVA_OPTS% %CATALINA_OPTS% %DEBUG_OPTS% -Djava.endorsed.dirs="%JAVA_ENDORSED_DIRS%" -classpath "%CLASSPATH%" -Dcatalina.base="%CATALINA_BASE%" -Dcatalina.home="%CATALINA_HOME%" -Djava.io.tmpdir="%CATALINA_TMPDIR%" %MAINCLASS% %CMD_LINE_ARGS% %ACTION% >> %CATALINA_BASE%\logs\catalina.out
goto end
:doSecurity
%_EXECJAVA% %JAVA_OPTS% %CATALINA_OPTS% %DEBUG_OPTS% -Djava.endorsed.dirs="%JAVA_ENDORSED_DIRS%" -classpath "%CLASSPATH%" -Djava.security.manager -Djava.security.policy=="%SECURITY_POLICY_FILE%" -Dcatalina.base="%CATALINA_BASE%" -Dcatalina.home="%CATALINA_HOME%" -Djava.io.tmpdir="%CATALINA_TMPDIR%" %MAINCLASS% %CMD_LINE_ARGS% %ACTION% >> %CATALINA_BASE%\logs\catalina.out
goto end
:doJpda
if not "%SECURITY_POLICY_FILE%" == "" goto doSecurityJpda
%_EXECJAVA% %JAVA_OPTS% %CATALINA_OPTS% -Xdebug -Xrunjdwp:transport=%JPDA_TRANSPORT%,address=%JPDA_ADDRESS%,server=y,suspend=n %DEBUG_OPTS% -Djava.endorsed.dirs="%JAVA_ENDORSED_DIRS%" -classpath "%CLASSPATH%" -Dcatalina.base="%CATALINA_BASE%" -Dcatalina.home="%CATALINA_HOME%" -Djava.io.tmpdir="%CATALINA_TMPDIR%" %MAINCLASS% %CMD_LINE_ARGS% %ACTION% >> %CATALINA_BASE%\logs\catalina.out
goto end
:doSecurityJpda
%_EXECJAVA% %JAVA_OPTS% %CATALINA_OPTS% -Xdebug -Xrunjdwp:transport=%JPDA_TRANSPORT%,address=%JPDA_ADDRESS%,server=y,suspend=n %DEBUG_OPTS% -Djava.endorsed.dirs="%JAVA_ENDORSED_DIRS%" -classpath "%CLASSPATH%" -Djava.security.manager -Djava.security.policy=="%SECURITY_POLICY_FILE%" -Dcatalina.base="%CATALINA_BASE%" -Dcatalina.home="%CATALINA_HOME%" -Djava.io.tmpdir="%CATALINA_TMPDIR%" %MAINCLASS% %CMD_LINE_ARGS% %ACTION% >> %CATALINA_BASE%\logs\catalina.out
goto end

posted @ 2010-12-27 12:32 afunms 阅读(3061) | 评论 (1) | 编辑收藏

NDP,NTDP

NDP Neighbor Discovery Protocol 邻居发现协议
NTDP Network Topology Discovery Protocol 网络拓扑发现协议

NDP（Neighbor Discovery Protocol）是用来发现邻接点相关信息的协议。支持设备都维护NDP邻居信息表，表项是可以老化的。当老化时间到，自动删除相应的表项。同时，用户可以清除当前的NDP 信息以重新收集邻接信息。
　　NTDP（Neighbor Topology Discovery Protocol）是用来收集网络拓扑信息的协议。NTDP 为集群管理提供可加入集群的设备信息，收集指定跳数内的交换机的拓扑信息。NDP 为NTDP 提供邻接表信息，NTDP 根据邻接信息发送和转发NTDP 拓扑收集请求，收集一定网络范围内每个设备的NDP 信息和它与所有邻居的连接信息。收集完这些信息后，管理设备或者网管可以根据需要使用这些信息，完成所需的功能。当成员设备上的NDP 发现邻居有变化时，通过握手报文将邻居改变的消息通知管理设备，管理设备可以启动NTDP 进行指定拓扑收集，从而使NTDP 能够及时反映网络拓扑的变化。

posted @ 2010-12-03 11:47 afunms 阅读(250) | 评论 (0) | 编辑收藏

用福建地名组成的祝福

生活如永定；价值如连城；
幸福如龙海；长寿比东山；
身体要永泰；事业定长泰；
生意拟建瓯；道路登上杭；
快乐永长乐；笑容如石狮；
人生愿福安；命运靠德化；
运气至将乐；财气冲云霄；
爱情似罗源；缘份聚浦城；
佳人倚屏南；秋眸透闽清；
生活悠宁德；稳定胜龙岩；
闲来学仙游；累了歇闽候；
悠然过连江；漫步武夷山；
春天踏漳浦；夏季潜安溪；
秋来往南靖；冬至望建阳；
客家祖长汀；土楼崇华安；
景美叹松溪；水幽赞尤溪；
世世祈诏安；代代久惠安；
居住乃福州；屋建依晋江；
家广置莆田；户望有霞浦；
雄伟大厦门；门奢赢金门；
饮水来泉州；想吃去沙县；
耕种有大田；丰收看古田；
心静能三明；神怡时南平；
大力举福鼎；脾性当平和；
人心慈平潭；量大自福清；
心静照明溪；为人切清流；
日子挺顺昌；滋润有光泽；
国盛须政和；民心盼永定；
乱世用武平；盛世民柘荣；
健康学邵武；产业富连城；
父母长寿宁；家人常泰宁；
交友圆周宁；诸事全宁化；
祈兄弟永安；祷爱人永春；
祝亲戚漳平；愿朋友南安；
风物满漳州；宝地属福建！

posted @ 2010-12-02 11:45 afunms 阅读(140) | 评论 (0) | 编辑收藏

问题进展

经过对揭阳数据的研究，我终于找到问题的根源。

1. 对路由的发现，以前的代码有点问题。又找出以前的论文，明确一下算法。

2. 揭阳设备路由表的nextHop全是VLAN。所以，这不是H3C或Cisco的问题。如果cisco这样设置，如果没有CDP，目前的程序一样得不出正确的结果。

3. 比较吃惊或者奇怪的是，H3C的设备有支持Bridge.mib，有的支持Q-brideg.mib，而有的二者都有。

4. 另一个，H3C的设备比较奇怪的是，它的bridge-mac不会出现在任何交换机的fdb表。因此，通用的二层链路发现算法无法运用。

5. 因为4，所以我只能从路由表进行发现，对于nextHop是VLAN，必须转成物理接口，然后用排除法（这个算法与通用二层链路算法有点类似，只是不用依赖bridge-mac）判断这条链路是否是真实的物理链路。

6. 根据5，修改了发现程序，对现在数据进行“发现”，得到了正确结果！

posted @ 2010-04-12 20:11 afunms 阅读(305) | 评论 (2) | 编辑收藏

在揭阳的三天三夜

04-07
1. 测试了现有的代码，仅找到很少的几条链路，而且结果还不正确。
2. 最奇怪的是，bridge.mib里的fdb表都没有数据，我的发现算法是基于fdb来作的，
fdb表没数据，肯定找不到链路。
3. 突然想起北京同事说的NDP，于是想用华为的NDP试试，加载huawei-hgmp.mib，
结果发现H3C的设备里根本没有数据，太失望了。

04-08
1. 想起三年前在安徽恒源的痛苦经历，但最终是用STP得到正确的结果。于是，我又试了
   基于STP的发现，还是没结果。为什么？因为STP里的数据不满足算法的要求。
2. 看来这次真的遇到挑战了。路由表里全是OSPF，我又想起曾经看过一篇文章，写的是基本
   OSPF的拓扑发现。在网上搜索了半天，只有万方的论文里有相关文章，无奈之下，只好用
   手机短信花了3块钱下了一篇论文。按论文里的算法，改了程序，经测试后，虽然有点进步，
   但仍有多台设备处于孤立状态，找不到链路，太郁闷了。
3. 用SolarWinds下载了所有h3c上的mib，回宾馆研究。发现SolarWinds在win7下的一个bug，
   导出功能完全不能用，我只好把结果存成txt。

04-09
1. 从下载的mib数据中惊奇地发现，h3c使用了Q-bridge而不是bridge，这就难怪bridge里的fdb
   表没有数据。这又让我心中燃起了希望。但Q-bridge里的address这一字段没数据，所以要用
   walk（而不是table）才能取到数据。
2. 专门写了一个取Q-bridge fdb表数据的类。核心交换h3c7510中的fdb表项巨大，大约有800条
   之多，snmp4j没取完就超时了，用SolarWinds也会出现超时的现象。
3. 再次测试了发现程序，由于有了fdb表的数据，多找出好多链路，但仍不完整。
4. 收集了所有设备的mib数据，回广州慢慢研究。

在揭阳的三天三夜，紧张而痛苦。我真的遇到一个大难题......

posted @ 2010-04-10 11:05 afunms 阅读(572) | 评论 (1) | 编辑收藏

MySQL存储过程和任务

stored procedure
创建
create procedure sp_name()
begin
………
end

调用
call sp_name()
注意：存储过程名称后面必须加括号，哪怕该存储过程没有参数传递

删除
drop procedure sp_name

其他
1.show procedure status
显示数据库中所有存储的存储过程基本信息，包括所属数据库，存储过程名称，创建时间等
2.show create procedure sp_name
显示某一个存储过程的详细信息

例子:
CREATE PROCEDURE `bag_app_flow`()
insert into bag_app_flow
select pid,avg(in_speed),avg(out_speed),max(log_time) log_time
from bag_app_flow_raw
where hour(now()) - hour(log_time) = 1
group by pid,date_format(log_time,'%Y-%m-%d %H');

--------------
event
使用下列的任意一句开启计划任务：
           SET GLOBAL event_scheduler = ON;
           SET @@global.event_scheduler = ON;
           SET GLOBAL event_scheduler = 1;
           SET @@global.event_scheduler = 1;
Event Scheduler创建的基本语法是：
          CREATE EVENT
          [IF NOT EXISTS]
          event_name
          ON SCHEDULE schedule
          [ON COMPLETION [NOT] PRESERVE]
          [ENABLE | DISABLE]
          [COMMENT 'comment']
          DO sql_statement
如果要调用procedure
    call sp_name() ,如
create event flow_job
on schedule every 1 hour
starts '2009-12-26 18:06:00'
do
call bag_ip_flow();
如果有多个procedures,则要加begin...end,如
create event flow_job
on schedule every 1 hour
starts '2009-12-26 18:06:00'
do
begin
call bag_app_flow();
call bag_ip_flow();
call bag_ip_group_flow();
end

posted @ 2009-12-26 18:59 afunms 阅读(232) | 评论 (0) | 编辑收藏

snmp trap处理

在研究了思科的Trap以及朗讯的Trap后，总结出处理trap的思路：

posted @ 2009-12-16 12:12 afunms 阅读(226) | 评论 (0) | 编辑收藏

JPCAP——JAVA中的数据链路层控制

摘要: JPCAP——JAVA中的数据链路层控制一．JPCAP简介众所周知，JAVA语言虽然在TCP/UDP传输方面给予了良好的定义，但对于网络层以下的控制，却是无能为力的。JPCAP扩展包弥补了这一点。 JPCAP实际上并非一个真正去实现对数据链路层的控制，而是一个中间件，JPCAP调用wincap/libpcap，而给JAVA语言提供一个公共的接口，从而实现了平台无关性。... 阅读全文

posted @ 2009-12-09 10:22 afunms 阅读(280) | 评论 (0) | 编辑收藏

kbps

码率就是数据传输时单位时间传送的数据位数，一般我们用的单位是kbps即千位每秒。
　　通俗一点的理解就是取样率，单位时间内取样率越大，精度就越高，处理出来的文件就越接近原始文件，但是文件体积与取样率是成正比的，所以几乎所有的编码格式重视的都是如何用最低的码率达到最少的失真，围绕这个核心衍生出来的cbr（固定码率）与vbr（可变码率），都是在这方面做的文章，不过事情总不是绝对的，从音频方面来说，码率越高，被压缩的比例越小，音质损失越小，与音源的音质越接近。
　　计算机中的信息都是二进制的0和1来表示，其中每一个0或1被称作一个位，用小写b表示，即bit（位）；大写B表示byte,即字节，一个字节＝八个位，即1B＝8b；前面的大写K表示千的意思，即千个位（Kb)或千个字节(KB)。表示文件的大小单位，一般都使用字节（KB）来表示文件的大小。
　　Kbps：首先要了解的是，ps指的是/s，即每秒。Kbps又称比特率，指的是数字信号的传输速率，也就是每秒钟传送多少个千位的信息（K表示千位，Kb表示的是多少千个位）；Kbps也可以表示网络的传输速度，为了在直观上显得网络的传输速度较快，一般公司都使用kb（千位）来表示，如果是KBps，则表示每秒传送多少千字节。1KByte/s＝8Kbps(一般简写为1KBps=8Kbps)。ADSL上网时的网速是512Kbps,如果转换成字节，就是512/8＝64KBps(即64千字节每秒）
　　在这里需要说明的问题是在单位换算上有一点是极其重要的即：1Mb=1024kb=1024000b 而1MB=1024KB=1024*1024B=1024*1024*8b=8388608b这在数量上差的很多
　　值得注意的是：
　　1KB=1024B=1024*8b 1kB=1000B=8000b
　　1Kb=1kb=1000b
　　在单位换算上一定要注意正常是以KBps来表示带宽
　　KBps与kBps的区别
　　小k代表kilo,千的意思，也就是1000，而B就是字节的意思，ps就是每秒的意思，那么连起来Bps就是字节每秒的意思。
　　那么kBps就是1000Bps也就是一千字节每秒的意思。
　　而大家都知道在电脑里，KB和B是不同的单位，他们之间换算是1KB=1024B的。
　　而KBps(K为大写字母)就等于1024Bps。而kBps（k为小写字母）的意思是千字节每秒。
　　千字节每秒(KBps）与一千字节每秒(kBps)是不同的。
　　KBps=1024Bps，kBps=1000Bps
　　也就是说KBps＞kBps [1]
　　人们常用Kbps形容音乐的听觉效果。
　　在WINDOWS 中它被称为“位速”，在一些播放器中被形容为“比特率”。
　　质量是指将数字声音由模拟格式转化成数字格式的采样率，采样率越高，还原后的音质就越好。
　　●Kbps值与现实音频对照：
　　16Kbps=电话音质
　　24Kbps=增加电话音质、短波广播、长波广播、欧洲制式中波广播
　　40Kbps=美国制式中波广播
　　56Kbps=话音
　　64Kbps=增加话音（手机铃声最佳比特率设定值、手机单声道MP3播放器最佳设定值）
　　112Kbps=FM调频立体声广播
　　128Kbps=磁带（手机立体声MP3播放器最佳设定值、低档MP3播放器最佳设定值）
　　160Kbps=HIFI高保真（中高档MP3播放器最佳设定值）
　　192Kbps=CD（高档MP3播放器最佳设定值）
　　256Kbps=Studio音乐工作室（音乐发烧友适用）
　　实际上随着技术的进步，音乐质量也越来越高，MP3的最高质量为320Kbps，但一些格式可以达到更高的质量和更高的音质。
　　比如正逐渐兴起的APE音频格式，能够提供真正发烧级的无损音质和相对于WAV格式更小的体积，其质量通常为550kbps-----950kbps。
　　其他：常见编码模式：
　　VBR（Variable Bitrate）动态比特率也就是没有固定的比特率，压缩软件在压缩时根据音频数据即时确定使用什么比特率，这是以质量为前提兼顾文件大小的方式，推荐编码模式；
　　ABR（Average Bitrate）平均比特率是VBR的一种插值参数。LAME针对CBR不佳的文件体积比和VBR生成文件大小不定的特点独创了这种编码模式。ABR在指定的文件大小内，以每50帧（30帧约1秒）为一段，低频和不敏感频率使用相对低的流量，高频和大动态表现时使用高流量，可以做为VBR和CBR的一种折衷选择。
　　CBR（Constant Bitrate），常数比特率指文件从头到尾都是一种位速率。相对于VBR和ABR来讲，它压缩出来的文件体积很大，而且音质相对于VBR和ABR不会有明显的提高。

posted @ 2009-12-01 10:40 afunms 阅读(264) | 评论 (0) | 编辑收藏

产品功能介绍

产品功能介绍

一、 网络管理

1. 网络拓扑自动发现。输入核心设备的IP地址或核心子网的网络地址，系统自动发现设备以及链路，完成后画出全网物理拓扑图。

2. 拓扑图展现。

① 将网络自动发现结果的以拓扑图的形式进行展示，提供设备、链路的实时信息。用户也可对该图进行自定义的布局。

② 不同设备类型以不同的图标进行展示，而且随着设备运行状态（CPU使用率、内存使用率和链路连通状态等）变化其图标颜色（蓝>黄>红）亦相应变化。

③ 可按IP或机器名搜索，快速定位到设备。

④ 可将拓扑图另存为JPG图片。

⑤ 鹰眼视图为全网络的缩略图，点击其中任一个点可定位到视图上的设备。

3．设备基本性能数据。CPU、内存、接口表、路由表、ARP表等。同时，可下载设备配置文件，以作备份。

二、 服务器管理

1．基本性能信息：CPU、内存、硬盘/文件系统利用率。

2．端口使用情况、进程存活、安装软件、裸文件（Aix）。

3．可采集服务器日志作统计分析。

三、 数据库管理

1. Oracle

①基本信息：所处的服务器名、数据库版本、大小。

②响应时间、用户连接数、用户权限角色。

③数据库状态、表空间利用率、数据库锁。

④ SGA击中率、用户会话、SQL执行情况。

2. MS-SQL

①基本信息：数据库所在的主机名、数据库版本、数据库文件路径。

②响应时间、缓存击中率、内存使用信息、查询页信息。

③事务锁等待时间、数据文件大小、活动用户数。

3. My-SQL

①基本信息：数据库所在操作系统的类型、数据库版本、数据库安装路径、数据文件路径。

②响应时间、每分钟请求数、每秒发送/接收字节数、连接信息、线程信息。

③表详细信息、用户会话。

四、 中间件管理

1. Weblogic

①基本信息：操作系统类型、版本、使用JAVA版本、提供者。

②响应时间、JVM使用率、JDBC连接池。

③线程池、web应用会话。

2. Websphere

①响应时间、JVM使用率。

② JDBC连接池、线程池、servlet会话。

3. Tomcat

①基本信息：Tomcat版本、操作系统类型、版本、JAVA版本、提供者。

②响应时间、链接器线程、JVM堆栈使用情况、服务器请求。

③数据库连接池、web会话。

五、Web服务器

1. HTTP URL

①页面大小。

②响应时间。

2. IIS

①响应时间。

② IIS里各网站的性能参数。

六、IP地址管理

1. 基于子网的IP地址分布图。

2. 基于子网的IP地址使用情况统计。

3. IP-MAC地址绑定，或者IP-MAC-交换机端口绑定。

4. IP定位：确定IP地址上联交换机的端口。

七、事件及告警管理

1. 可接收设备Syslog数据，按关键字匹配把Syslog转成系统告警。

2. 可接收设备SNMP Trap数据，可处理通用Trap数据。同时，可按产商私有MIB来翻译产商特殊的Trap数据，并转换成系统告警（需定制开发）。

曾经成功完成对朗读ATM交换机Trap数据的完全解析。

3. 告警设置不仅限于阀值越界告警，还有属性匹配告警、属性变化告警以及实体增加或删除告警。

4. 告警分析实现告警压缩、告警合并（告警根源分析）、告警升级以及告警恢复通知。

5. 告警通知方式：Email、声音、弹出窗口和手机短信。

6. 控制告警通知方式：连续式（每产生一次告警都发通知）、跳跃式（每隔3次告警才发通知）和一次式（仅发一次通知）。

八、报表管理

1. 网络设备整体性能报表。

2. 服务器整体性能报表。

3．网络设备接口性能报表。

4．服务器接口性能报表。

九、流量管理

1. 支持Netflow V5和V9。

2. 对于较小的网络（设备数在100内），可以用交换机端口镜像（span）。系统用JPCAP采集原始数据。

十、可定制开发其它功能，比如实现对防火墙、防病毒系统和IDS的日志采集和分析。

系统截图

http://www.blogjava.net/afunms/gallery/43080.html

posted @ 2009-11-30 20:33 afunms 阅读(270) | 评论 (0) | 编辑收藏

jar命令

用jar打包classes，老是会忘记

C:\java\jdk1.6.0_03\bin>jar cvf c:/nms.jar classes/*.*

posted @ 2009-11-27 17:19 afunms 阅读(156) | 评论 (0) | 编辑收藏

ATM网的拓扑发现

ATM网的拓扑发现，在网上根本找不到相关资料，经过自己长时间的研究，终于有了结果。经过实际验证，证明是正确的。

其实它比IP网的拓扑发现要简单得多。

获取PVC：

PSAX ATM中有4种PVC：

ATM2ATM PVC

cirEm2ATM PVC

bridge2ATM PVC

gige2ATM PVC

由于在acmib中没有定义gige2ATM PVC，所以只能找到其他三种PVC。

三种PVC的获取方法：

PVC	Table	OID
ATM2ATM	atmPvcVccTable	1.3.6.1.4.1.1751.2.18.6.1.1
cirEm2ATM	cirEmAtmPvcVccTable	1.3.6.1.4.1.1751.2.18.6.6.1
bridge2ATM	bridgeAtmPvcVccTable	1.3.6.1.4.1.1751.2.18.6.13.1

算法：

(1) 找出所有active的pvc。

(2) pvc相同且pvc的服务类型(serviceType)相同的两个atm之间存在一条物理链路。这两表中sreviceType的代码所表示的serviceType不相同，比如在atmPvcVccTable中serviceType定义为

SYNTAX INTEGER {

ubr(1),

vbr-nrt2(2),

vbr-nrt1(3),

vbr-rt2(4),

vbr-rt1(5),

vbr-express(6),

cbr4(7),

cbr3(8),

cbr2(9),

cbr1(10),

gfr2(11)

}

而在cirEmAtmPvcVccTable中为

SYNTAX INTEGER {

cbr-1(1),

cbr-2(2),

cbr-3(3),

cbr-4(4)

}

所以不能比较数字，而应该比较字符串。

(3) 要得到pvc及其所在的接口，就必须得到三个表中的index，以bridgePvcVccTable为例：

以第一行来说明 1305001.101001.11.260

1305001 interface sideA

101001 interface sideB

11.260 即PVC

所以在台ATM中11-260这条PVC就是接在sideB（为什么取sideB而不是sideA？我现在还不明白）101001这个接口上。Interface的格式为SSPPCCC，以此得到物理接口0101。

有些链路找不到，可以肯定地说，是因为找不到gige2ATM pvc。

posted @ 2009-10-29 21:55 afunms 阅读(248) | 评论 (0) | 编辑收藏

PSAX Trap 翻译(4)

有了以上三张表，很容易把PSAX Trap翻译过来：

/**

* 翻译snmp trap

*/

private String translatePsaxTrap(Connection conn,SnmptrapDto dto) throws Exception{

StringBuffer trap = new StringBuffer(200);

Statement stat = conn.createStatement();

String oid = dto.getOid() + "." + dto.getSpecifics();

ResultSet rs = stat.executeQuery("select b.description from acmib_oid a,acmib_event b where a.oid='" + oid + "' and a.symbol=b.symbol");

if(rs.next())

trap.append(rs.getString(1));

String[] msgs = dto.getMessage().split(",");

/**

* 过滤掉最后一行1.3.6.1.4.1.1751.2.18.1.146.

*/

for(int i=0;i < msgs.length - 1;i++){

String[] _msgs = msgs[i].split("=");

String _oid = _msgs[0].substring(0,_msgs[0].length() - 3); //去掉最后.0

String _value = _msgs[1].trim();

rs = stat.executeQuery("select * from acmib_oid where oid='" + _oid + "'");

if(rs.next()){

trap.append(rs.getString("symbol")).append("=").append(_msgs[1]);

if(rs.getString("symbol").endsWith("Code")){

ResultSet _rs = stat.executeQuery("select * from acmib_code where symbol='" + rs.getString("symbol") + "' and code=" + _value);

if(_rs.next())

trap.append("[").append(_rs.getString("description")).append("]");

}

trap.append(",");

}

return trap.toString();

}

（这里省略了接受SNMP Trap的代码）

举例1：
Trap原包内容：
oid=1.3.6.1.4.1.1751.2.18.8.4
specifics=67
message=
1.3.6.1.4.1.1751.2.18.6.31.1.1.0 = 1309001,
1.3.6.1.4.1.1751.2.18.6.33.1.1.0 = 14,
1.3.6.1.4.1.1751.2.18.6.33.1.2.0 = 153,
1.3.6.1.4.1.1751.2.18.6.33.1.3.0 = 45:86:20:02:00:88:01:00:0f:00:00:00:00:00:00:06:00:90:01:77,
1.3.6.1.4.1.1751.2.18.6.33.1.4.0 = 301001,
1.3.6.1.4.1.1751.2.18.6.33.1.5.0 = 0,
1.3.6.1.4.1.1751.2.18.6.33.1.6.0 = 669,
1.3.6.1.4.1.1751.2.18.1.146.1.1.0 = 100286

翻译后：
Notification that a SPVC connection between ATM and ATM endpoints has been deleted. spvcAddrIfA= 1309001,
atmAtmSpvcVccVpiA= 14,
atmAtmSpvcVccVciA= 153,
atmAtmSpvcVccRemoteAtmPortAddr= 45:86:20:02:00:88:01:00:0f:00:00:00:00:00:00:06:00:90:01:77,
atmAtmSpvcVccIfB= 301001,
atmAtmSpvcVccVpiB= 0,
atmAtmSpvcVccVciB= 669,
（这个atmAtmSpvcVccRemoteAtmPortAddr应该能转成一个IP或Interface，暂时没搞明白）
很明显，可以明白是一条ATM2ATM的SPVC被删除。

举例2：
Trap原包内容：
oid=1.3.6.1.4.1.1751.2.18.8.3
specifics=104
message=
1.3.6.1.4.1.1751.2.18.15.2.0 = 1309001,
1.3.6.1.4.1.1751.2.18.15.4.0 = 67,
1.3.6.1.4.1.1751.2.18.1.146.1.1.0 = 100374,
翻译后：
Notification that a interface has undergone reduction in bandwidth. Critical depending on Failure Reason Code.interfaceIndex= 1309001,interfaceFailureReasonCode= 67[newBWBelowCurrentAllocated]
可以看明白，是一个通道的带宽被改小了。

posted @ 2009-10-24 01:16 afunms 阅读(115) | 评论 (0) | 编辑收藏

PSAX Trap 翻译(3)

最后，用mibble把acmib所有代码和它相应的描述导入数据库。

/**

* 导入acmib中所有类型代码与描述的对映

*/

public void importCode(){

MibBrowser mb = new MibBrowser();

Mib mib = mb.getMib("e:/ACMIB.mib");

List mvss = (List)mib.getAllSymbols();

Connection conn = ConnectionManager.getConnection();

int id = 1;

try{

Statement stat = conn.createStatement();

for(int i=0,n=mvss.size();i<n;i++){

if(mvss.get(i) instanceof MibValueSymbol

&& ((MibValueSymbol)mvss.get(i)).getType() instanceof SnmpObjectType) {

MibValueSymbol mvs = (MibValueSymbol)mvss.get(i);

SnmpObjectType soType = (SnmpObjectType)mvs.getType();

if(soType.getSyntax() instanceof IntegerType){

IntegerType intType = (IntegerType)soType.getSyntax();

MibValueSymbol[] itss = intType.getAllSymbols();

if(itss.length > 0)

for(int j=0;j < itss.length;j++){

stat.addBatch("insert into acmib_code(id,symbol,code,description)values("

+ id + ",'" + mvs.getName() + "'," + itss[j].getValue() + ",'" + itss[j].getName() + "')");

id++;

}

if( id % 100 == 0)

stat.executeBatch();

}

stat.executeBatch();

}catch(Exception e){

e.printStackTrace();

}

结果如下：

这样，为翻译psax trap的所有的基础数据都准备好了。

posted @ 2009-10-23 13:59 afunms 阅读(121) | 评论 (0) | 编辑收藏

PSAX Trap 翻译(2)

接着，用mibble把acmib中所有事件导入数据库：

/**

* 导入事件

*/

public void importEvent(){

MibBrowser mb = new MibBrowser();

Mib mib = mb.getMib("e:/ACMIB.mib");

List mvss = (List)mib.getAllSymbols();

Connection conn = ConnectionManager.getConnection();

int id = 1;

try{

Statement stat = conn.createStatement();

for(int i=0,n=mvss.size();i<n;i++){

if(mvss.get(i) instanceof MibValueSymbol

&& ((MibValueSymbol)mvss.get(i)).getType() instanceof SnmpNotificationType) {

MibValueSymbol mvs = (MibValueSymbol)mvss.get(i);

SnmpNotificationType snt = (SnmpNotificationType)mvs.getType();

String descr = null;

String originDescr = null;

if(snt.getDescription().indexOf(":") > 0)

descr = snt.getDescription().substring(snt.getDescription().indexOf(":") + 2);

else

descr = snt.getDescription();

if(descr.indexOf("Return value") > 0)

descr = descr.substring(0,descr.indexOf("Return value"));

if(descr.indexOf("Data send with the trap") > 0)

descr = descr.substring(0,descr.indexOf("Data send with the trap"));

descr = descr.replaceAll("\n", " ");

descr = descr.replaceAll("'", "''");

originDescr = snt.getDescription().replaceAll("'", "''");

stat.addBatch("insert into acmib_event(id,symbol,description,origin_description)values(" + id + ",'" + mvs.getName() + "','" + descr + "','" + originDescr + "')");

id++;

if( id % 100 == 0)

stat.executeBatch();

}

stat.executeBatch();

}catch(Exception e){

e.printStackTrace();

}

结果如下：

posted @ 2009-10-22 10:52 afunms 阅读(94) | 评论 (0) | 编辑收藏

PSAX Trap 翻译(1)

今天终于实现把朗讯PSAX ATM交换机的SNMP Trap翻译成明文的功能。前后花了四天的时间。

开始，我想用mibble把acmib完全解析出来，但折腾了一整天，都没有结果，至少最重要的OID是终始出不来，可能是我不会用mibble吧。

接着换种思路，用SolarWinds（一个很好用的mib browser）把acmib copy成纯文本。

文本如下：

acMIB 1.3.6.1.4.1.1751.2.18

connectionConfig 1.3.6.1.4.1.1751.2.18.6

atmAtmSpvcVccTable 1.3.6.1.4.1.1751.2.18.6.33

atmAtmSpvcVccEntry 1.3.6.1.4.1.1751.2.18.6.33.1

atmAtmSpvcVccStatsInOdometerCellCountHiB 1.3.6.1.4.1.1751.2.18.6.33.1.50

atmAtmSpvcVccStatsInOdometerCellCountLoA 1.3.6.1.4.1.1751.2.18.6.33.1.47

atmAtmSpvcVccStatsInOdometerCellCountLoB 1.3.6.1.4.1.1751.2.18.6.33.1.51

atmAtmSpvcVccStatsOdometerReset 1.3.6.1.4.1.1751.2.18.6.33.1.55

atmAtmSpvcVccStatsOdometerTimer 1.3.6.1.4.1.1751.2.18.6.33.1.54

atmAtmSpvcVccStatsOutCellCountHiA1.3.6.1.4.1.1751.2.18.6.33.1.37

atmAtmSpvcVccStatsOutCellCountHiB1.3.6.1.4.1.1751.2.18.6.33.1.41

atmAtmSpvcVccStatsOutCellCountLoA 1.3.6.1.4.1.1751.2.18.6.33.1.38

atmAtmSpvcVccStatsOutCellCountLoB 1.3.6.1.4.1.1751.2.18.6.33.1.42

atmAtmSpvcVccStatsOutOdometerCellCountHiA1.3.6.1.4.1.1751.2.18.6.33.1.48

atmAtmSpvcVccStatsOutOdometerCellCountHiB1.3.6.1.4.1.1751.2.18.6.33.1.52

atmAtmSpvcVccStatsOutOdometerCellCountLoA 1.3.6.1.4.1.1751.2.18.6.33.1.49

atmAtmSpvcVccStatsOutOdometerCellCountLoB 1.3.6.1.4.1.1751.2.18.6.33.1.53

atmAtmSpvcVccStatsTimer 1.3.6.1.4.1.1751.2.18.6.33.1.43

atmAtmSpvcVccSusCellRateA2B 1.3.6.1.4.1.1751.2.18.6.33.1.10

atmAtmSpvcVccSusCellRateB2A 1.3.6.1.4.1.1751.2.18.6.33.1.16

atmAtmSpvcVccTfcDescModify 1.3.6.1.4.1.1751.2.18.6.33.1.70

atmAtmSpvcVccTrafficShapingA2B 1.3.6.1.4.1.1751.2.18.6.33.1.64

atmAtmSpvcVccTrafficShapingB2A 1.3.6.1.4.1.1751.2.18.6.33.1.65

atmAtmSpvcVccType 1.3.6.1.4.1.1751.2.18.6.33.1.20

atmAtmSpvcVccVciA 1.3.6.1.4.1.1751.2.18.6.33.1.2

atmAtmSpvcVccVciB 1.3.6.1.4.1.1751.2.18.6.33.1.6

atmAtmSpvcVccViA 1.3.6.1.4.1.1751.2.18.6.33.1.56

……

把这个文本导入数据库：

/**

* acmib.mib有两个版本,此方法把两个版本中数据都导入数据库.

* 但保证不会有重复的oid

*/

public void importOid(){

Connection conn = ConnectionManager.getConnection();

try{

Statement stat = conn.createStatement();

BufferedReader in1 = new BufferedReader(new FileReader("e:/acmib.txt"));

String row = null;

int id = 1;

while((row=in1.readLine())!=null){

int loc = row.indexOf("1.3.6.");

String symbol = row.substring(0, loc - 1).trim();

String oid = row.substring(loc).trim();

stat.addBatch("insert into acmib_oid(id,oid,symbol)values(" + id + ",'" + oid + "','" + symbol + "')");

id++;

if( id % 100 == 0)

stat.executeBatch();

}

stat.executeBatch();

ResultSet rs = stat.executeQuery("select oid from acmib_oid order by oid");

List<String> oids = new ArrayList<String>();

while(rs.next())

oids.add(rs.getString(1));

BufferedReader in2 = new BufferedReader(new FileReader("e:/acmib2.txt"));

while((row=in2.readLine())!=null){

String[] rowCols = row.split(" ");

if(oids.contains(rowCols[2])) continue;

stat.addBatch("insert into acmib_oid(id,oid,symbol)values(" + id + ",'" + rowCols[2] + "','" + rowCols[1] + "')");

id++;

if( id % 100 == 0)

stat.executeBatch();

}

stat.executeBatch();

}catch(Exception e){

e.printStackTrace();

}

结果如下：

posted @ 2009-10-21 10:47 afunms 阅读(230) | 评论 (0) | 编辑收藏

国庆江西之行

2009年10月江西之行:
庐山--九江--南昌

到目前为止，我走过的地方：
吉林：长春
辽宁：沈阳
河北：秦皇岛、衡水
北京
山东：济南、淄博、潍坊、泰安
安徽：淮北
江苏：徐州
重庆
陕西：安康
江西：南昌、九江
福建：福州、厦门、泉州、漳州、龙岩、南平、三明
广东：广州、佛山、中山、韶关、惠州、云浮、河源、阳江、潮州、茂名

posted @ 2009-10-08 11:32 afunms 阅读(151) | 评论 (0) | 编辑收藏

我们的新产品

posted @ 2009-09-25 15:08 afunms 阅读(208) | 评论 (2) | 编辑收藏

接口性能各指标的计算公式

在rfc1213.mib，接口组中：
if InOctets --接口发送的字节数
ifOutOctets --接口接收到的字节数
if InUcastPkts --输入的单播包数
ifOutUcastPkts --输出的单播包数
if InNUcastPkts --输入的非单播包数
ifOutNUcastPkts --输出的非单播包数
if InDiscards --接口丢弃的输入包数
ifOutDiscards --接口丢弃的输出包数
if InErrors --包含错误的输入包数
ifOutErrors --包含错误的输出包数
ifinUnkownProtos --由于定向到一个未知或
不支持的协议而被丢弃的包数
ifOutQlen --输出队列中的所有包数
portName --端口的名称

性能管理应用一般要观察接口的利用率、错误
率、丢包率等。这些性能参数都分为输入和输出两
种情况。下面给出计算公式:
输入利用率= (Δif InOctets * 8) / (ifSpeed * T) * 100 %
输出利用率= (ΔifOutOctets * 8) / (ifSpeed * T) * 100 %
输入差错率= Δif InErrors/ (Δif InUcastPks + Δif InNucastPks) * 100 %
输出差错率= ΔifOutErrors/ (ΔifOutUcastPks + ΔifOutNucastPks) * 100 %
输入丢包率=Δif InDiscards/ T
输出丢包率=ΔifOutDiscards/ T

posted @ 2009-07-31 08:38 afunms 阅读(1702) | 评论 (0) | 编辑收藏

opennms discovery模块中的两个问题.

DiscoveryLink.java

1.对ARP表发现时,以下代码有问题:

/**

* 在XX的网络中测试,以下这段代码不正确.确切地说应该是对华为设备不成立,对其他设备还是可以

* 的opennms的程序员在写程序时肯定是没有接触华为的设备.(2009.7.25)

*/

if (isMacIdentifierOfBridgeNode(macAddress)) {

if (log().isInfoEnabled())

log().info("run: at interface " + macAddress

+ " belongs to bridge node! Not adding to discoverable atinterface.");

macsExcluded.add(macAddress);

continue;

}

2. 对Route表发现时,以下代码也有问题:

/**

* 这个if语句不适合,也许opennms的牛人只考虑FastEthernet接口

*/

if (snmpiftype == SNMP_IF_TYPE_ETHERNET) {

if (log().isInfoEnabled())

log().info("run: Ethernet interface for nodeid. Skipping ");

continue;

}

posted @ 2009-07-25 08:48 afunms 阅读(241) | 评论 (0) | 编辑收藏

纪念波仔

与你同事一年多，你的敬业精神和技术水平都给大家留下很深的印象。

今天见你最后一眼，突然间，我哭了。
明天是父亲节，初为人父的你，还没来得及享受这个天伦之乐就匆匆离去.....

但愿你在另一个世界不再受病魔的折磨！
同时祝你的家人平安幸福。

posted @ 2009-06-20 23:10 afunms 阅读(126) | 评论 (0) | 编辑收藏

一张专家推荐的最健康的作息时间表

   7:30：起床。英国威斯敏斯特大学的研究人员发现，那些在早上5:22—7:21分起床的人，其血液中有一种能引起心脏病的物质含量较高，因此，在7:21之后起床对身体健康更加有益。打开台灯。“一醒来，就将灯打开，这样将会重新调整体内的生物钟，调整睡眠和醒来模式。”拉夫堡大学睡眠研究中心教授吉姆·霍恩说。喝一杯水。水是身体内成千上万化学反应得以进行的必需物质。早上喝一杯清水，可以补充晚上的缺水状态。
   7:30—8:00：在早饭之前刷牙。“在早饭之前刷牙可以防止牙齿的腐蚀，因为刷牙之后，可以在牙齿外面涂上一层含氟的保护层。要么，就等早饭之后半小时再刷牙。”英国牙齿协会健康和安全研究人员戈登·沃特金斯说。
   8:00—8:30：吃早饭。“早饭必须吃，因为它可以帮助你维持血糖水平的稳定，”伦敦大学国王学院营养师凯文·威尔伦说。早饭可以吃燕麦粥等，这类食物具有较低的血糖指数。
   8:30—9:00：避免运动。来自布鲁奈尔大学的研究人员发现，在早晨进行锻炼的运动员更容易感染疾病，因为免疫系统在这个时间的功能最弱。步行上班。马萨诸塞州大学医学院的研究人员发现，每天走路的人，比那些久坐不运动的人患感冒病的几率低25%。
   9:30：开始一天中最困难的工作。纽约睡眠中心的研究人员发现，大部分人在每天醒来的一两个小时内头脑最清醒。
   10:30：让眼睛离开屏幕休息一下。如果你使用电脑工作，那么每工作一小时，就让眼睛休息3分钟。
   11:00：吃点水果。这是一种解决身体血糖下降的好方法。吃一个橙子或一些红色水果，这样做能同时补充体内的铁含量和维生素C含量。
   13:00：在面包上加一些豆类蔬菜。你需要一顿可口的午餐，并且能够缓慢地释放能量。“烘烤的豆类食品富含纤维素，番茄酱可以当作是蔬菜的一部分。”维伦博士说。
   14:30—15:30：午休一小会儿。雅典的一所大学研究发现，那些每天中午午休30分钟或更长时间，每周至少午休3次的人，因心脏病死亡的几率会下降37%。
   16:00：喝杯酸奶。这样做可以稳定血糖水平。在每天三餐之间喝些酸牛奶，有利于心脏健康。
   17:00—19:00：锻炼身体。根据体内的生物钟，这个时间是运动的最佳时间，舍菲尔德大学运动学医生瑞沃·尼克说。
   19:30：晚餐少吃点。晚饭吃太多，会引起血糖升高，并增加消化系统的负担，影响睡眠。晚饭应该多吃蔬菜，少吃富含卡路里和蛋白质的食物。吃饭时要细嚼慢咽。
   21:45：看会电视。这个时间看会儿电视放松一下，有助于睡眠，但要注意，尽量不要躺在床上看电视，这会影响睡眠质量。
   23:00：洗个热水澡。“体温的适当降低有助于放松和睡眠。”拉夫堡大学睡眠研究中心吉姆·霍恩教授说。
   23:30：上床睡觉。如果你早上7点30起床，现在入睡可以保证你享受8小时充足的睡眠。

posted @ 2009-06-14 11:47 afunms 阅读(128) | 评论 (0) | 编辑收藏

SQL ' 转义字符

例：select * from tbl where uyear='''06'

请注意其中红色背景的单引号，它即表示转义字符，如果我们省略，则整个语句会出错，转义字符不会输出，上例中 uyear 的实际条件值为 '06，而不是 ''06

为什么不能省略呢，假如我们省略，上句变成：select * from tbl where uyear=''06'

由于在 SQL 中单引号表示字符串的开始和结束符号，于是 SQL 解释器会认为语句中灰色背景的为字符串，其后的语句显然是个错误的语句，当然会报错，为了解决字符串的单引号问题，就出现了转义字符单。

解决了我的一个大问题，不然程序就要大改了。

posted @ 2009-06-13 21:16 afunms 阅读(537) | 评论 (0) | 编辑收藏

Oracle buys Sun for US$7.4 bln

Source: CCTV.com
04-21-2009 13:29
Oracle Corporation has snapped up computer server and software maker Sun Microsystems for 7.4 billion US dollars. It trumped rival IBM's attempt to buy one of Silicon Valley's best known, and most troubled, companies.

Monday's deal comes after a month-long drama that entered its final chapter last week. IBM had retracted an earlier buyout offer after the two sides couldn't agree on key details.

Oracle has traditionally been a business software maker. It will now be able to use Sun's assets to build a more comprehensive one-stop technology shop. The deal gives Oracle ownership of the Java programming language, which runs on more than a billion devices around the world.

今天在电视上听到这消息，真是挺吃惊的。对于一个长期从事Java开发的程序员来说，对Sun有一种特殊的感情。现在Sun突然从地球上消失了。。。。，很难接受这样的事实。

posted @ 2009-04-21 21:53 afunms 阅读(176) | 评论 (1) | 编辑收藏

workflow

http://en.wikipedia.org/wiki/Workflow

A workflow is a depiction of a sequence of operations, declared as work of a person, work of a simple or complex mechanism, work of a group of persons,work of an organization of staff, or machines. Workflow may be seen as any abstraction of real work, segregated in workshare, work split or whatever types of ordering. For control purposes, workflow may be a view on real work under a chosen aspect,thus serving as a virtual representation of actual work. The flow being described often refers to a document that is being transferred from one step to another.

A workflow is a model to represent real work for further assessment, e.g., for describing a reliably repeatable sequence of operations. More abstractly, a workflow is a pattern of activity enabled by a systematic organization of resources, defined roles and mass, energy and information flows, into a work process that can be documented and learned.Workflows are designed to achieve processing intents of some sort, such as physical transformation, service provision, or information processing.

Workflow concepts are closely related to other concepts used to describe organizational structure, such as silos, functions, teams, projects, policies and hierarchies. Workflows may be viewed as one primitive building block of organizations. The relationships among these concepts are described later in this entry.

The term workflow is used in computer programming to capture and develop human to machine interaction. Workflow software aims to provide end users with an easier way to orchestrate or describe complex processing of data in a visual form, much like flow charts but without the need to understand computers or programming.

posted @ 2009-03-07 10:23 afunms 阅读(152) | 评论 (0) | 编辑收藏

OSWorkflow Tomcat5.5 JDBC配置

(1)   创建MySQL数据库osworkflow
          新建osworkflow数据库，然后导入osworkflow\src\etc\deployment\jdbc\mysql.sql
(2)   在Tomcat下创建配置文件
          tomcat5.5.23\conf\Catalina\localhost\osworkflow.xml
<?xml version='1.0' encoding='utf-8'?>
<Context path="/osworkflow" debug="0" reloadable="true">
<Resource
name="jdbc/DefaultDS"
type="javax.sql.DataSource"
driverClassName="com.mysql.jdbc.Driver"
maxIdle="10"
maxWait="5000"
username="root"
password="root"
url="jdbc:mysql://localhost:3306/osworkflow?useUnicode=true&characterEncoding=utf-8"
maxActive="20"/>
</Context>
(3)修改WEB-INF\classes\osuser.xml
<opensymphony-user>
    <provider class="com.opensymphony.user.provider.jdbc.JDBCAccessProvider">
    <property name="user.table">os_user</property>
    <property name="group.table">os_group</property>
    <property name="membership.table">os_membership</property>
    <property name="user.name">username</property>
    <property name="user.password">passwordhash</property>
    <property name="group.name">groupname</property>
    <property name="membership.userName">username</property>
    <property name="membership.groupName">groupname</property>
    <property name="datasource">jdbc/DefaultDS</property>
    </provider>
    <provider class="com.opensymphony.user.provider.jdbc.JDBCCredentialsProvider">
       <property name="user.table">os_user</property>
    <property name="group.table">os_group</property>
    <property name="membership.table">os_membership</property>
    <property name="user.name">username</property>
    <property name="user.password">passwordhash</property>
    <property name="group.name">groupname</property>
    <property name="membership.userName">username</property>
    <property name="membership.groupName">groupname</property>
    <property name="datasource">jdbc/DefaultDS</property>
    </provider>
    <provider class="com.opensymphony.user.provider.jdbc.JDBCProfileProvider">
       <property name="user.table">os_user</property>
    <property name="group.table">os_group</property>
    <property name="membership.table">os_membership</property>
    <property name="user.name">username</property>
    <property name="user.password">passwordhash</property>
    <property name="group.name">groupname</property>
    <property name="membership.userName">username</property>
    <property name="membership.groupName">groupname</property>
    <property name="datasource">jdbc/DefaultDS</property>
    </provider>
<authenticator class="com.opensymphony.user.authenticator.SmartAuthenticator" />
</opensymphony-user>

posted @ 2009-02-22 21:24 afunms 阅读(505) | 评论 (0) | 编辑收藏

研究工作流

以前我对工作流根本没概念，但研究了OSWorkflow，特别是看了网上那个例子后，突然间豁然开朗。如果不是研究工作流，我从不认为系统中“组织架构”模块会如此复杂。公司的OA为什么不可扩展，就是因为“组织架构”设计得很不合理。

posted @ 2009-02-21 12:01 afunms 阅读(127) | 评论 (0) | 编辑收藏

TestCase

A test case in software engineering is a set of conditions or variables under which a tester will determine whether an application or software system meets specifications. The mechanism for determining whether a software program or system has passed or failed such a test is known as a test oracle. In some settings an oracle could be a requirement or use case. It may take many test cases to determine that a software program or system is functioning correctly. Test cases are often referred to as test scripts, particularly when written. Written test cases are usually collected into test suites.

Formal, requirement-based test cases
In order to fully test that all the requirements of an application are met, there must be at least one test case for each requirement unless a requirement has sub-requirements. In that situation, each sub-requirement must have at least one test case. This is frequently done using a traceability matrix. Some methodologies, like RUP, recommend creating at least two test cases for each requirement. One of them should perform positive testing of requirement and other should perform negative testing. Written test cases should include a description of the functionality to be tested, and the preparation required to ensure that the test can be conducted.

What characterizes a formal, written test case is that there is a known input and an expected output, which is worked out before the test is executed. The known input should test a precondition and the expected output should test a postcondition.

posted @ 2009-02-19 22:07 afunms 阅读(189) | 评论 (0) | 编辑收藏

Test my program

Tested configuration and discovery modules,this is the first time I test my program so carefully.Since SV2.0 has much bug,now I am aware of the importance of testing.

I tested the following cases:

Configuration

1. Add a network device to the network device list

2. Add a server to the server list

3. Remove a network device from the network device list

4. Remove a server from the server list

5. Add a network device to the server list(failure is correct)

6. Add a server to the network device list(failure is correct)

7. Add a link road

8. Remove a link road

9. Query a server/network device/link according to the given condition

Discovery

10. Totally new discover a network configuration

11. Re-discover a network configuration

12. Remove a network configuration

posted @ 2009-02-18 22:09 afunms 阅读(126) | 评论 (0) | 编辑收藏

惠州之行

行程：
2月11日下午惠州ZFW 给客户培训SourceView基本操作
2月11日下午惠州GA 产品推广
2月12日上午惠州JCY 产品推广

bug：
1. IP资源没有数据；
2. 数据库某个表字段太短，字值插不进去；
3. 报表页面上有-1，没有处理；
4. 子网网关有NULL，干脆在页面上隐藏“网关”这列。

另，用户要求增加短信报警的功能。

总结：
1. 现在用户的技术水平也在提高，这对我们的专业水平、我们的产品质量都提出了更高的要求；
2. 市场潜力大，但不同的用户需求可能差别很大，这就要求我们的产品要有很强的扩展性。

posted @ 2009-02-12 12:02 afunms 阅读(107) | 评论 (0) | 编辑收藏

NodeManager

摘要: 今天终于把NodeManager的接口确定下来了。代码不知改了多少次，才成为今天这个样子，每个接口都有明确的定义和责任，真是不容易。2.0中这块写得极混乱，代码重用性不好，可扩展性受到很大影响。3.0中能把NodeManager的接口设计好，算是整个架构的一个重大改进。 NodeManager完成以下功能： 1．加入网元前，检查用户输入的参数，以及这个网元是否已经存在... 阅读全文

posted @ 2009-01-25 17:06 afunms 阅读(353) | 评论 (0) | 编辑收藏

3.0discovery模块总结

1. 解决了有时发现程序结束不了的问题，根本原因在于有一个set没有同步，改为

hasDetected = Collections.synchronizedSet(new HashSet<String>())

后，问题解决。

2. 更改了路由发现中关于子网的一个bug：

原代码：

if(!pool.existSubnet(subnet)){

engine.addSubnet(subnet);

router.addSubnet(subnet);

}

改为：

Subnet subnet = pool.getSubnetByIP(item.getDest());

if(subnet==null){ //if subnet doesn't exist

subnet = new Subnet();

subnet.setNetAddress(item.getDest());

subnet.setNetMask(item.getNetMask());

engine.addSubnet(subnet);

}

router.addSubnet(subnet);

3. 2.0中只能对一个网络进行发现，3.0可以对多个网络进行发现，画出多个拓扑图。

4. 2.0中只能有一个发现范围，3.0可以增加多个发现范围。

5. 2.0中各表之间没有关联，初始化时要执行多条SQL代码，3.0中利用表外键，
只要删除一条记录，就可以删除所有相关数据。

6. 3.0在发现完之后，保存所有设备的SNMP表数据。

7. 3.0为再发现留有接口，使拓扑再发现成为可能，只是暂时没时间去实现。

8. 拓扑节点排序算法以及拓扑图的生成

排序算法 MapCompositor 给它节点以及连接，按一定算法计算出各节点的位置坐标。
DefaultCompositor实现接口computeCoordinate，把节点按排成若干个圆。

用DefaultMapBuilder dmb = new DefaultMapBuilder();

dmb.buildMap(config.getId());

来测试排序算法，因为它不要用到内存中的数据，直接取数据库的数据。

发现执行的是 NewDiscoveryVisitor.buildDefaultMap()

调用发现后内存中的数据。

9．增加网络设备的服务器时，可以重用发现模块中的代码。在2.0中是专门写了一长串代码，
与发现模块没关系。

posted @ 2009-01-24 22:21 afunms 阅读(284) | 评论 (1) | 编辑收藏

对添加网络设备的处理

对于在发现之后，再添加一个网络设备的处理有点麻烦。我认为除了增加设备本身还应该找出它与即有设备之间的链路，这必然要重用发现模块的代码，会造成代码的混乱，但这不是关键。关键如果在这个过程中“发现”出了异常，程序无法返回，会给用户奇怪的感觉。

目前的代码是按我的想法实现的，在公司的网络环境中测试中通过了。但不能保证在其他复杂的环境中得到一样的结果。

posted @ 2009-01-21 11:34 afunms 阅读(160) | 评论 (0) | 编辑收藏

Modules of SourceView3.0

Modules of SourceView3.0:

1. Topology Discovery:System initializes,discovering all devices and the links among them.Devices includes routers,switches,route switches,ATM Switches and servers.

2. Configuration Management:Manages all of IT elements in NMS,including network devices,servers,DBs,midwares and web-servers.Add elements intoNMS,remove elements from it and so on.

3. Report Management:Defines some useful reports,users can review the performance data of any IT elements through these reports.

4. Business View:Users can define a view by themselves.The elements associate with the specified business system that they concern would be dragged into this view.

5. Topology View: Shows network topology and reflects real running status of the entire network.e.g.traffic of links.

6. Fault Management:Analyses the performance data collected by monitors,if it violates the rules defined by users,NMS would alarm immediately.

7. Performance Management:Collects performance data from IT elements by all Kinds of monitors.

posted @ 2009-01-20 21:49 afunms 阅读(206) | 评论 (0) | 编辑收藏

布什告别演说

THE PRESIDENT: Fellow citizens: For eight years, it has been my honor to serve as your President. The first decade of this new century has been a period of consequence — a time set apart. Tonight, with a thankful heart, I have asked for a final opportunity to share some thoughts on the journey that we have traveled together, and the future of our nation.

Five days from now, the world will witness the vitality of American democracy. In a tradition dating back to our founding, the presidency will pass to a successor chosen by you, the American people. Standing on the steps of the Capitol will be a man whose history reflects the enduring promise of our land. This is a moment of hope and pride for our whole nation. And I join all Americans in offering best wishes to President-Elect Obama, his wife Michelle, and their two beautiful girls.

Tonight I am filled with gratitude — to Vice President Cheney and members of my administration; to Laura, who brought joy to this house and love to my life; to our wonderful daughters, Barbara and Jenna; to my parents, whose examples have provided strength for a lifetime. And above all, I thank the American people for the trust you have given me. I thank you for the prayers that have lifted my spirits. And I thank you for the countless acts of courage, generosity, and grace that I have witnessed these past eight years.

This evening, my thoughts return to the first night I addressed you from this house — September the 11th, 2001. That morning, terrorists took nearly 3,000 lives in the worst attack on America since Pearl Harbor. I remember standing in the rubble of the World Trade Center three days later, surrounded by rescuers who had been working around the clock. I remember talking to brave souls who charged through smoke-filled corridors at the Pentagon, and to husbands and wives whose loved ones became heroes aboard Flight 93. I remember Arlene Howard, who gave me her fallen son’s police shield as a reminder of all that was lost. And I still carry his badge.

As the years passed, most Americans were able to return to life much as it had been before 9/11. But I never did. Every morning, I received a briefing on the threats to our nation. I vowed to do everything in my power to keep us safe.

Over the past seven years, a new Department of Homeland Security has been created. The military, the intelligence community, and the FBI have been transformed. Our nation is equipped with new tools to monitor the terrorists’ movements, freeze their finances, and break up their plots. And with strong allies at our side, we have taken the fight to the terrorists and those who support them. Afghanistan has gone from a nation where the Taliban harbored al Qaeda and stoned women in the streets to a young democracy that is fighting terror and encouraging girls to go to school. Iraq has gone from a brutal dictatorship and a sworn enemy of America to an Arab democracy at the heart of the Middle East and a friend of the United States.

There is legitimate debate about many of these decisions. But there can be little debate about the results. America has gone more than seven years without another terrorist attack on our soil. This is a tribute to those who toil night and day to keep us safe — law enforcement officers, intelligence analysts, homeland security and diplomatic personnel, and the men and women of the United States Armed Forces.

Our nation is blessed to have citizens who volunteer to defend us in this time of danger. I have cherished meeting these selfless patriots and their families. And America owes you a debt of gratitude. And to all our men and women in uniform listening tonight: There has been no higher honor than serving as your Commander-in-Chief.

The battles waged by our troops are part of a broader struggle between two dramatically different systems. Under one, a small band of fanatics demands total obedience to an oppressive ideology, condemns women to subservience, and marks unbelievers for murder. The other system is based on the conviction that freedom is the universal gift of Almighty God, and that liberty and justice light the path to peace.

This is the belief that gave birth to our nation. And in the long run, advancing this belief is the only practical way to protect our citizens. When people live in freedom, they do not willingly choose leaders who pursue campaigns of terror. When people have hope in the future, they will not cede their lives to violence and extremism. So around the world, America is promoting human liberty, human rights, and human dignity. We’re standing with dissidents and young democracies, providing AIDS medicine to dying patients — to bring dying patients back to life, and sparing mothers and babies from malaria. And this great republic born alone in liberty is leading the world toward a new age when freedom belongs to all nations.

For eight years, we’ve also strived to expand opportunity and hope here at home. Across our country, students are rising to meet higher standards in public schools. A new Medicare prescription drug benefit is bringing peace of mind to seniors and the disabled. Every taxpayer pays lower income taxes. The addicted and suffering are finding new hope through faith-based programs. Vulnerable human life is better protected. Funding for our veterans has nearly doubled. America’s air and water and lands are measurably cleaner. And the federal bench includes wise new members like Justice Sam Alito and Chief Justice John Roberts.

When challenges to our prosperity emerged, we rose to meet them. Facing the prospect of a financial collapse, we took decisive measures to safeguard our economy. These are very tough times for hardworking families, but the toll would be far worse if we had not acted. All Americans are in this together. And together, with determination and hard work, we will restore our economy to the path of growth. We will show the world once again the resilience of America’s free enterprise system.

Like all who have held this office before me, I have experienced setbacks. There are things I would do differently if given the chance. Yet I’ve always acted with the best interests of our country in mind. I have followed my conscience and done what I thought was right. You may not agree with some of the tough decisions I have made. But I hope you can agree that I was willing to make the tough decisions.

The decades ahead will bring more hard choices for our country, and there are some guiding principles that should shape our course.

While our nation is safer than it was seven years ago, the gravest threat to our people remains another terrorist attack. Our enemies are patient, and determined to strike again. America did nothing to seek or deserve this conflict. But we have been given solemn responsibilities, and we must meet them. We must resist complacency. We must keep our resolve. And we must never let down our guard.

At the same time, we must continue to engage the world with confidence and clear purpose. In the face of threats from abroad, it can be tempting to seek comfort by turning inward. But we must reject isolationism and its companion, protectionism. Retreating behind our borders would only invite danger. In the 21st century, security and prosperity at home depend on the expansion of liberty abroad. If America does not lead the cause of freedom, that cause will not be led.

As we address these challenges — and others we cannot foresee tonight — America must maintain our moral clarity. I’ve often spoken to you about good and evil, and this has made some uncomfortable. But good and evil are present in this world, and between the two of them there can be no compromise. Murdering the innocent to advance an ideology is wrong every time, everywhere. Freeing people from oppression and despair is eternally right. This nation must continue to speak out for justice and truth. We must always be willing to act in their defense — and to advance the cause of peace.

President Thomas Jefferson once wrote, “I like the dreams of the future better than the history of the past.” As I leave the house he occupied two centuries ago, I share that optimism. America is a young country, full of vitality, constantly growing and renewing itself. And even in the toughest times, we lift our eyes to the broad horizon ahead.

I have confidence in the promise of America because I know the character of our people. This is a nation that inspires immigrants to risk everything for the dream of freedom. This is a nation where citizens show calm in times of danger, and compassion in the face of suffering. We see examples of America’s character all around us. And Laura and I have invited some of them to join us in the White House this evening.

We see America’s character in Dr. Tony Recasner, a principal who opened a new charter school from the ruins of Hurricane Katrina. We see it in Julio Medina, a former inmate who leads a faith-based program to help prisoners returning to society. We’ve seen it in Staff Sergeant Aubrey McDade, who charged into an ambush in Iraq and rescued three of his fellow Marines.

We see America’s character in Bill Krissoff — a surgeon from California. His son, Nathan — a Marine — gave his life in Iraq. When I met Dr. Krissoff and his family, he delivered some surprising news: He told me he wanted to join the Navy Medical Corps in honor of his son. This good man was 60 years old — 18 years above the age limit. But his petition for a waiver was granted, and for the past year he has trained in battlefield medicine. Lieutenant Commander Krissoff could not be here tonight, because he will soon deploy to Iraq, where he will help save America’s wounded warriors — and uphold the legacy of his fallen son.

In citizens like these, we see the best of our country - resilient and hopeful, caring and strong. These virtues give me an unshakable faith in America. We have faced danger and trial, and there’s more ahead. But with the courage of our people and confidence in our ideals, this great nation will never tire, never falter, and never fail.

It has been the privilege of a lifetime to serve as your President. There have been good days and tough days. But every day I have been inspired by the greatness of our country, and uplifted by the goodness of our people. I have been blessed to represent this nation we love. And I will always be honored to carry a title that means more to me than any other - citizen of the United States of America.

And so, my fellow Americans, for the final time: Good night. May God bless this house and our next President. And may God bless you and our wonderful country. Thank you. (Applause.)

2009.1.15 8:14 P.M. EST

posted @ 2009-01-16 20:25 afunms 阅读(308) | 评论 (0) | 编辑收藏

改进后的发现结果

今天在公司测试SourceView3.0发现程序，找出所有支持SNMP的设备以及它们的链路，
包括服务器到交换机的链路：

Discovery log:

2009-01-15 14:09:44 - INFO - ----[SourceView3.0]Starting ----

2009-01-15 14:09:45 - INFO - Parsing configuration file [struts-default.xml]

2009-01-15 14:09:45 - INFO - Parsing configuration file [struts-plugin.xml]

2009-01-15 14:09:45 - INFO - Parsing configuration file [struts.xml]

2009-01-15 14:09:45 - INFO - Overriding property struts.i18n.reload - old value: false new value: true

2009-01-15 14:10:45 - INFO - 新主机加入：

1.路由器:ip=192.168.0.254,

sysOid=1.3.6.1.4.1.9.1.110,

sysName=C3640,

community=cisco,

symbol=cisco

---------------------

2009-01-15 14:10:46 - INFO - 新子网加入：

Subnet.2.addr[192.168.0.0],mask[255.255.255.0]

2009-01-15 14:10:56 - INFO - 新主机加入：

3.路由交换机:ip=192.168.0.253,

sysOid=1.3.6.1.4.1.9.1.633,

sysName=3560,

community=cisco,

mac=00:19:55:d9:9c:80,

symbol=cisco

---------------------

2009-01-15 14:10:57 - INFO - 新链路加入：

4.C3640[Ethernet0/1]<-->3560[Fa0/23],[route link](路由器到三层交换机)

2009-01-15 14:10:57 - INFO - 新子网加入：

Subnet.5.addr[192.168.1.0],mask[255.255.255.0]

2009-01-15 14:10:57 - INFO - 新子网加入：

Subnet.6.addr[192.168.2.0],mask[255.255.255.128]

2009-01-15 14:10:57 - INFO - 新子网加入：

Subnet.7.addr[192.168.2.128],mask[255.255.255.240]

2009-01-15 14:10:57 - INFO - 新子网加入：

Subnet.8.addr[192.168.3.0],mask[255.255.255.0]

2009-01-15 14:10:57 - INFO - 新子网加入：

Subnet.9.addr[192.168.4.0],mask[255.255.255.0]

2009-01-15 14:10:57 - INFO - 新子网加入：

Subnet.10.addr[192.168.5.0],mask[255.255.255.0]

2009-01-15 14:10:57 - INFO - 新子网加入：

Subnet.11.addr[192.168.6.0],mask[255.255.255.0]

2009-01-15 14:12:08 - INFO - 新主机加入：

12.路由交换机:ip=192.168.3.252,

sysOid=1.3.6.1.4.1.2011.2.23.22,

sysName=Quidway,

community=cisco,

mac=00:e0:fc:0c:9d:1b,

symbol=huawei

---------------------

2009-01-15 14:12:58 - INFO - 新主机加入：

13.服务器:ip=192.168.2.133,

sysOid=1.3.6.1.4.1.2.3.1.2.1.1.3,

sysName=localhost,

community=public,

symbol=aix

---------------------

2009-01-15 14:15:18 - INFO - 新主机加入：

14.服务器:ip=192.168.2.18,

sysOid=1.3.6.1.4.1.311.1.1.3.1.2,

sysName=SOFTDEPT18,

community=public,

symbol=windows

---------------------

2009-01-15 14:15:58 - INFO - ----discovering Layer 2 using the common method----

2009-01-15 14:15:58 - INFO - 新链路加入：

15.3560[Fa0/14]<-->localhost[en0; Product: PCI Ethernet Adapter (23100020) Man],[arp link](服务器到三层交换机)