Welcome my space's@jedellniu

msn新病毒: 每当我开机登陆msn的时候, msn自动发心信息给我的msn上的好友, 真是烦啊~!````` 天天都是这样```类似以前qq尾巴, 前段文字为汉字,后面跟带一个网址;  这个病毒是我上中国缘那个网站www.meet8.com以后就天天这样子了~```, 开机开msn就自动给msn上的在线用户发信息, 烦死人了~!

    

信息内容为:     "加入，送股，试试。顺便帮我刷点分   http://www.life365world.org "

                   " 大家08年事业顺心, 人顺财顺事事顺~`````
                   http://www.meet8.com/member/regist_stock.html?inviterid=2477004&invitertype=42"

                   "好啊.. 想死你么了..
                   http://www.meet8.com/member/regist_stock.html?inviterid=2477004&invitertype=42"

                   "这是我中国缘的空间.你有吗?有的别忘记告诉我啊!
                   http://www.meet8.com/member/regist_stock.html?inviterid=2477004&invitertype=42"

                   "这是我中国缘的空间.你有吗?有的别忘记告诉我啊!
                   http://www.meet8.com/member/regist_stock.html?inviterid=2477004&invitertype=42    "

 

在网上找了也没找到能够解决的方法, 火急啊~~````` 求大侠们帮忙啊~~!!!!!!!

自己通过以下三种方法解决都无济于事``````   

      1) 360安全卫士通杀   2)卡巴7.0注册版通杀  3)自己在系统注册表里搜索相关信息内容删除 

这三部都做过了还是不起作用, 发贴敬请各位大哥大侠们帮忙啊~!!!!!!

发表于：2008年1月8日 13时19分38秒阅读(0)评论(0)特效：[图]
本文链接: http://user.qzone.qq.com/249433686/blog/1199769578
IETF RFC 1213/RFC1213
链接地址: http://www.rfc-archive.org/getrfc.php?rfc=1213

IETF RFC 1213 / RFC1213
 Management Information Base for Network Management of TCP/IP-based internets:MIB-II

Network Working Group                                      K. McCloghrie
Request for Comments: 1213                      Hughes LAN Systems, Inc.
Obsoletes: RFC 1158                                              M. Rose
                                       Performance Systems International
                                                                 Editors
                                                              March 1991

           Management Information Base for Network Management
                       of TCP/IP-based internets:
                                 MIB-II

 Status of this Memo

   This memo defines the second version of the Management Information
   Base (MIB-II) for use with network management protocols in TCP/IP-
   based internets.  This RFC specifies an IAB standards track protocol
   for the Internet community, and requests discussion and suggestions
   for improvements.  Please refer to the current edition of the "IAB
   Official Protocol Standards" for the standardization state and status
   of this protocol.  Distribution of this memo is unlimited.

 Table of Contents

   1. Abstract...............................................    2
   2. Introduction ..........................................    2
   3. Changes from RFC 1156 .................................    3
   3.1 Deprecated Objects ...................................    3
   3.2 Display Strings ......................................    4
   3.3 Physical Addresses ...................................    4
   3.4 The System Group .....................................    5
   3.5 The Interfaces Group .................................    5
   3.6 The Address Translation Group ........................    6
   3.7 The IP Group .........................................    6
   3.8 The ICMP Group .......................................    7
   3.9 The TCP Group ........................................    7
   3.10 The UDP Group .......................................    7
   3.11 The EGP Group .......................................    7
   3.12 The Transmission Group ..............................    8
   3.13 The SNMP Group ......................................    8
   3.14 Changes from RFC 1158 ................. .............    9
   4. Objects ...............................................   10
   4.1 Format of Definitions ................................   10
   5. Overview ..............................................   10
   6. Definitions ...........................................   12
   6.1 Textual Conventions ..................................   12
   6.2 Groups in MIB-II .....................................   13
   6.3 The System Group .....................................   13

SNMP Working Group                                          Page 1 

RFC 1213                         MIB-II                       March 1991

   6.4 The Interfaces Group .................................   16
   6.5 The Address Translation Group ........................   23
   6.6 The IP Group .........................................   26
   6.7 The ICMP Group .......................................   41
   6.8 The TCP Group ........................................   46
   6.9 The UDP Group ........................................   52
   6.10 The EGP Group .......................................   54
   6.11 The Transmission Group ..............................   60
   6.12 The SNMP Group ......................................   60
   7. Acknowledgements ......................................   67
   8. References ............................................   69
   9. Security Considerations ...............................   70
   10. Authors' Addresses ...................................   70

1.  Abstract

   This memo defines the second version of the Management Information
   Base (MIB-II) for use with network management protocols in TCP/IP-
   based internets.  In particular, together with its companion memos
   which describe the structure of management information (RFC 1155)
   along with the network management protocol (RFC 1157) for TCP/IP-
   based internets, these documents provide a simple, workable
   architecture and system for managing TCP/IP-based internets and in
   particular the Internet community.

2.  Introduction

   As reported in RFC 1052, IAB Recommendations for the Development of
   Internet Network Management Standards [1], a two-prong strategy for
   network management of TCP/IP-based internets was undertaken.  In the
   short-term, the Simple Network Management Protocol (SNMP) was to be
   used to manage nodes in the Internet community.  In the long-term,
   the use of the OSI network management framework was to be examined.
   Two documents were produced to define the management information: RFC
   1065, which defined the Structure of Management Information (SMI)
   [2], and RFC 1066, which defined the Management Information Base
   (MIB) [3].  Both of these documents were designed so as to be
   compatible with both the SNMP and the OSI network management
   framework.

   This strategy was quite successful in the short-term: Internet-based
   network management technology was fielded, by both the research and
   commercial communities, within a few months.  As a result of this,
   portions of the Internet community became network manageable in a
   timely fashion.

   As reported in RFC 1109, Report of the Second Ad Hoc Network
   Management Review Group [4], the requirements of the SNMP and the OSI

 

SNMP Working Group                                          Page 2 

RFC 1213                         MIB-II                       March 1991

   network management frameworks were more different than anticipated.
   As such, the requirement for compatibility between the SMI/MIB and
   both frameworks was suspended.  This action permitted the operational
   network management framework, the SNMP, to respond to new operational
   needs in the Internet community by producing this document.

   As such, the current network management framework for TCP/IP- based
   internets consists of: Structure and Identification of Management
   Information for TCP/IP-based internets, RFC 1155 [12], which
   describes how managed objects contained in the MIB are defined;
   Management Information Base for Network Management of TCP/IP-based
   internets: MIB-II, this memo, which describes the managed objects
   contained in the MIB (and supercedes RFC 1156 [13]); and, the Simple
   Network Management Protocol, RFC 1098 [5], which defines the protocol
   used to manage these objects.

3.  Changes from RFC 1156

   Features of this MIB include:

   (1)  incremental additions to reflect new operational
        requirements;

   (2)  upwards compatibility with the SMI/MIB and the SNMP;

   (3)  improved support for multi-protocol entities; and,

   (4)  textual clean-up of the MIB to improve clarity and
        readability.

   The objects defined in MIB-II have the OBJECT IDENTIFIER prefix:

      mib-2      OBJECT IDENTIFIER ::= { mgmt 1 }

   which is identical to the prefix used in MIB-I.

3.1.  Deprecated Objects

   In order to better prepare implementors for future changes in the
   MIB, a new term "deprecated" may be used when describing an object.
   A deprecated object in the MIB is one which must be supported, but
   one which will most likely be removed from the next version of the
   MIB (e.g., MIB-III).

   MIB-II marks one object as being deprecated:

      atTable

SNMP Working Group                                          Page 3 

RFC 1213                         MIB-II                       March 1991

   As a result of deprecating the atTable object, the entire Address
   Translation group is deprecated.

   Note that no functionality is lost with the deprecation of these
   objects: new objects providing equivalent or superior functionality
   are defined in MIB-II.

3.2.  Display Strings

   In the past, there have been misinterpretations of the MIB as to when
   a string of octets should contain printable characters, meant to be
   displayed to a human.  As a textual convention in the MIB, the
   datatype

      DisplayString ::=
          OCTET STRING

   is introduced.  A DisplayString is restricted to the NVT ASCII
   character set, as defined in pages 10-11 of [6].

   The following objects are now defined in terms of DisplayString:

      sysDescr
      ifDescr

   It should be noted that this change has no effect on either the
   syntax nor semantics of these objects.  The use of the DisplayString
   notation is merely an artifact of the explanatory method used in
   MIB-II and future MIBs.

   Further it should be noted that any object defined in terms of OCTET
   STRING may contain arbitrary binary data, in which each octet may
   take any value from 0 to 255 (decimal).

3.3.  Physical Addresses

   As a further, textual convention in the MIB, the datatype

      PhysAddress ::=
          OCTET STRING

   is introduced to represent media- or physical-level addresses.

   The following objects are now defined in terms of PhysAddress:

      ifPhysAddress
      atPhysAddress
      ipNetToMediaPhysAddress

 

SNMP Working Group                                          Page 4 

RFC 1213                         MIB-II                       March 1991

   It should be noted that this change has no effect on either the
   syntax nor semantics of these objects.  The use of the PhysAddress
   notation is merely an artifact of the explanatory method used in
   MIB-II and future MIBs.
 
...............

表于：2008年1月8日 11时22分39秒阅读(1)评论(0)
文链接:http://user.qzone.qq.com/249433686/blog/1199762559

 

fcaps是国际电联的标准模型，为企业管理水平。

The five FCAPS domains are:五fcaps领域分别是：

F ault Management f ault      故障管理

C onfiguration Management   配置管理

A ccounting Management A ccounting      计费管理

P erformance Management p erformance     性能管理

S ecurity Management     安全管理

 

Fault Management故障管理

Fault management is the domain where network problems are discovered and corrected.故障管理是域网络的地方，发现问题和纠正。

Steps are then taken to prevent them from occurring or recurring.步骤，然后采取，以防止他们发生或复发。

By doing so, the network remains operational and downtime is minimized.这样，网络仍然是业务和停机时间减少到最低限度。

Configuration Management配置管理

Configuration management is where daily operations are monitored and controlled.配置管理是日常运作进行监控和控制。

All hardware and programming changes are coordinated.所有的硬件和节目的变化，重视协调发展。

In addition, new programs, new equipment, modification of existing systems and the removal of obsolete systems and programs are also coordinated.此外，新节目，新设备，改造现有的制度和去除过时的制度和程序也相协调。

Accounting Management 计费管理

Accounting management is devoted to determining how to optimally distribute resources among enterprise subscribers.会计管理，是专门以确定如何以最佳方式分配资源，其中企业用户。

This helps to minimize the cost of operations by making the most effective use of the systems available.这有利于最大限度地减少经营成本，使最有效地利用该系统提供的。

This level is also responsible for ensuring the appropriate billing of users.这一级也有责任确保适当的计费用户。

Performance Management 性能管理

Performance management is involved in managing the overall performance of the enterprise network.绩效管理是参与管理的整体表现，企业网络。 Potential problems are identified, throughput is maximized and bottlenecks are identified.潜在问题，确定后，吞吐量最大化和瓶颈确定。 Improvements that will yield the greatest enhancement to overall performance are identified.改善，将能取得最大的提升，以整体表现确定。

Security Management安全管理

Security management is responsible for protecting the network from unauthorized users and physical and electronic sabotage.安全管理是负责保护网络免受未经授权的用户和物理和电子破坏。

Security management is responsible for user authentication and authorization.安全管理部门负责用户认证和授权。

It also maintains the confidentiality of user information.它也保持了保密的用户信息。