Technical Committee LAN Emulation Servers Management Specification
1.0
af-lane-0057.000
March 1996
LAN Emulation Servers Management Specification 1.0
af-lane-0057.000
March 1996
(C) 1996 The ATM Forum. All Rights Reserved. No part of this publication may be reproduced in any form or by any means.
The information in this publication is believed to be accurate as of its publication date. Such information is subject to change without notice and the ATM Forum is not responsible for any errors. The ATM Forum does not assume any responsibility to update or correct any information in this publication. Notwithstanding anything to the contrary, neither The ATM Forum nor the publisher make any representation or warranty, expressed or implied, concerning the completeness, accuracy, or applicability of any information contained in this publication. No liability of any kind shall be assumed by The ATM Forum or the publisher as a result of reliance upon any information contained in this publication.
The receipt or any use of this document or its contents does not in any way create by implication otherwise:
?Any express or implied license or right to or under any ATM Forum member company's patent, copyright, trademark or trade secret rights which are or may be associated with the ideas,
techniques, concepts or expressions contained herein; nor
?Any warranty or representation that any ATM Forum member companies will announce any product(s) and/or service(s) related thereto, or if such announcements are made, that such announced product(s) and/or service(s) embody any or all of the ideas, technologies, or concepts contained herein; nor
?Any form of relationship between any ATM Forum member companies and the recipient or user of this document.
Implementation or use of specific ATM standards or recommendations and ATM Forum specifications will be voluntary, and no company shall agree or be obliged to implement them by virtue of participation in The ATM Forum.
The ATM Forum is a non-profit international organization accelerating industry cooperation on ATM technology. The ATM Forum does not, expressly or otherwise, endorse or promote any specific products or services.
NOTE: The user's attention is called to the possibility that implementation of the ATM interoperability specification contained herein may require use of an invention covered by patent rights held by ATM Forum Member companies or others. By publication of this ATM interoperability specification, no position is taken by The ATM Forum with respect to validity of any patent claims or of any patent rights related thereto or the ability to obtain the license to use such rights. ATM Forum Member companies agree to grant licenses under the relevant patents they own on reasonable and nondiscriminatory terms and conditions to applicants desiring to obtain such a license. For additional information contact:
The ATM Forum
Worldwide Headquarters
2570 West El Camino Real
Suite 304
Mountain View, CA 94040
Tel: +1-415-949-6700
Fax: +1-415-949-6705
LAN Emulation Servers Management Specification 1.0 af-lane-0057.000
Acknowledgement
The contributions adopted by the ATM Forum and the assistance by the editing group of the LAN Emulation Sub-working Group, who contributed text and reviewed the contributions were essential to this specification.
In particular, the editor would like to recognise members who made significant contributions to this effort: Chris Young
Ian Griffiths
Prakash Desai
The assistance by these members and all who participated in the LAN Emulation Sub-working Group, especially chairman Keith McCloghrie is appreciated.
Faye Ly, Editor
ATM Forum Technical Committee Page 1
1. Introduction________________________________________________________3 1.1 Abbreviations_________________________________________________________________3
1.2 References___________________________________________________________________4
2. Management Functions_______________________________________________5 2.1 Configuration Management______________________________________________________5 2.2 Performance Management_______________________________________________________5 2.3 Fault Management_____________________________________________________________5 2.4 Security Management__________________________________________________________5
2.5 Accounting Management________________________________________________________5
3. Management Framework_____________________________________________6 3.1 The SNMP Network Management Framework_______________________________________6 3.2 Requirements for LAN Emulation Servers__________________________________________6
3.2.1 Requirements for SNMP____________________________________________________6
3.3 MIB Conventions_____________________________________________________________6
4. MIB-II and other MIB support_________________________________________8 4.1 MIB II support________________________________________________________________8
4.2 AToMMIB Support____________________________________________________________8
5. Emulated LAN MIB Description________________________________________9 5.1 Management model____________________________________________________________9 5.2 MIB Groups__________________________________________________________________9
5.2.1 ELAN Administration Group________________________________________________10
5.2.2 ELAN Configuration Group_________________________________________________10
5.2.3 LECS Configuration Group_________________________________________________12
5.2.4 LECS Statistics Group_____________________________________________________13
This table lists all counters associated with the LECS this agent maintains.________________13
5.2.5 LECS Fault Management Group_____________________________________________13
6. LAN Emulation Server MIB Description_________________________________15 6.1 Management model___________________________________________________________15 6.2 MIB Organisation____________________________________________________________15 6.3 MIB Groups_________________________________________________________________15
6.3.1 LES Configuration Group__________________________________________________15
6.3.2 LES Statistics Group______________________________________________________16
6.3.3 LES-LEC Statistics Group__________________________________________________16
6.3.4 LES Fault Management Group______________________________________________16
7. Broadcast and Unknown Server MIB description__________________________18 7.1 Management model___________________________________________________________18 7.2 MIB Organisation____________________________________________________________18 7.3 MIB Groups_________________________________________________________________18
7.3.1 BUS Configuration Group__________________________________________________18
7.3.2 BUS Statistics Group______________________________________________________18
7.4.2 BUS Fault Management Group______________________________________________19
8. LAN Emulation Servers MIB Definitions_________________________________20
1.Introduction
ATM LAN Emulation emulates services of existing LANs across an ATM network. It provides a MAC layer service, specifically Ethernet/IEEE 802.3 and IEEE 802.5, over an ATM network. LAN emulation is described in the ATM Forum document “LAN Emulation Over ATM Specification - Version 1.0” [1]. This document describes how to manage some of the components in the LAN Emulation.
The LAN Emulation specification 1.0 defines four components: LEC (LAN Emulation Client), LES (LAN Emulation Server), BUS (Broadcast and Unknown Server) and LECS (LAN Emulation Configuration Server). LES, BUS and LECS provide various services to enable communication between LECs, and are referred to in this document collectively as ‘LAN Emulation servers’.
This document defines the management information for LES, BUS and LECS. The management information of the LEC is defined in [6]. This specification include three MIB modules. The ELAN MIB provides ELAN configuration and LECS management information. The LECS management group is mandatory if and only if the LECS is implemented. The LAN Emulation LES MIB covers LES management information, and BUS MIB provides BUS management information.
1.1Abbreviations
The following acronyms are used throughout this document.
AAL ATM Adaptation Layer
ATM Asynchronous Transfer Mode
BUS Broadcast and Unknown Server
ELAN Emulated Local Area Network
LAN Local Area Network
LANE LAN Emulation
LE LAN Emulation
LE_ARP LAN Emulation Address Resolution Protocol
LEC LAN Emulation Client
LECS LAN Emulation Configuration Server
LES LAN Emulation Server
LNNI LAN Emulation Network-Network Interface
LUNI LAN Emulation User-Network Interface
MAC Media Access Control
RD Route Descriptor
RFC Request For Comment (Document Series)
UNI User-Network Interface
VCC Virtual Channel Connection
VCI Virtual Channel Identifier
VPI Virtual Path Identifier
1.2References
[1] The ATM Forum, LAN Emulation Over ATM Specification, Version 1.0.
[2] RFC 1213, McCloghrie and Rose, Management Information Base for Network Management of TCP/IP-based internets: MIB-II.
[3] RFC 1573, McCloghrie and KastenHoltz, Evolution of the Interfaces Group of MIB-II.
[4] RRC 1695, Ahmed and Tesink, Definitions of Managed Objects for ATM Management.
[5] Internet Drafts, Ly, Noto, Smith, Tesink, Definitions of Supplemental Managed Objects for ATM Management. (draft-ietf-atommib-atm2-01.txt)
[6] The ATM Forum. LAN Emulation Client Management: Version 1.0 Specification.
[7] RFC 1442, Case, McCloghrie, Rose and Waldbusser, Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2).
[8] RFC 1445, Galvin and McCloghrie, Administrative Model for version 2 of the Simple Network Management Protocol (SNMPv2).
[9] RFC 1448, Case, McCloghrie, Rose and Waldbusser, Protocol Operations for version 2 of the Simpel Network Management Protocol (SNMPv2).
[10] RFC 1443, Case, McCloghrie, Rose and Waldbusser, Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2).
2.Management Functions
Network management can be divided into the areas of configuration, performance, fault, security, and accounting management.
2.1Configuration Management
The MIBs enable network managers to:
? create and destroy Emulated LANs (ELANs)
? assign clients to and delete them from an ELAN
? control the parameters of the LECS, LES and BUS
? monitor ELAN topology, e.g. which LECs are joined to a LES
? identify the VCCs being used by the LES or BUS
No information is provided about VCCs beyond describing which are being used. Management of VCC configuration is specified in [4] and [5]. Management issues relating to the LANE server-to-server (LNNI) protocol are outside the scope of this specification because at time of writing the Forum work on this topic is not complete. It is however a design goal to make the MIB modules easy to extend to accommodate the future LNNI support, and it is anticipated that this will be done in a future revision of these MIBs once the LNNI protocols have been published by the ATM Forum.
2.2Performance Management
Network managers can obtain statistics for ELAN server components. These are collected for every server and also for each server-client pairing. While LES- and BUS-related statistics are located in the LES MIB and BUS MIB respectively, LECS statistics (along with all other LECS management) are to be found in the optional LECS part of the ELAN MIB.
2.3Fault Management
The MIBs contain Facilities for detection of problems in an ELAN that are caused by the failures detected by service components. Information is provided as follows:
? operational status is available for each service component (indicates server is ‘up’ or ‘down’)
? error logs are maintained for each service component (see section 5 for details)
2.4Security Management
Security management is outside the scope of this version of the LAN Emulation Server Management specification.
2.5Accounting Management
Accounting management is outside the scope of this version of the LAN Emulation Server Management specification.
3.Management Framework
The network management framework for LAN Emulation Servers is defined using SNMP MIBs. SNMP is an Internet-standard network management framework of which there are currently more than one versions. The MIB modules specified in this document are both compliant to the SNMPv2, and semantically identical to the peer SNMPv1 definitions. This specification does not mandate the use of SNMPv2. RFC 1452 describes how SNMPv1 and SNMPv2 coexist, and The Simple Times reports that automatic translations can be obtained by mailing SNMPv2 MIBs to mib-v2tov1@https://www.doczj.com/doc/6b10143884.html,.
3.1The SNMP Network Management Framework
The SNMP Network Management Framework are defined in the RFCs Since the SNMP is still evolving, this document only lists a few RFCs that are related.. They are:
? RFC 1442 [7] which defines the SMI, the mechanisms used for describing and naming objects for the purpose of management
? STD 17, RFC 1213 [2] defines MIB-II, the core set of managed objects for the Internet suite of protocols
? RFC 1445 [8] which defines the administrative and other architectural aspects of the framework ? RFC 1448 [9] which defines the protocol used for network access to managed objects
? RFC 1443 [10] which defines the textual conventions used by network management information definitions
The Framework permits new objects to be defined for the purpose of experimentation and evaluation.
3.2Requirements for LAN Emulation Servers
The LAN Emulation Server and Broadcast and Unknown Server should be network manageable either via the SNMP network management protocol or via some other network management protocol. The management of the LAN Emulation Configuration Server is required only for the system that implements it.
3.2.1Requirements for SNMP
SNMP agents that support LAN Emulation Configuration Servers, LAN Emulation Servers and Broadcast and Unknown Servers MUST implement:
? Three MIB modules defined in this specification: ELAN MIB, LES MIB and BUS MIB
3.3MIB Conventions
The following convention is used in the MIB definitions in this specification: When a table is defined to allow row creation and deletion or to be read-creatable, the RowStatus object is required in the ‘create’ or
‘destroy’ operation. This operation is performed on the row indicated by the instance given in the SNMP request.
RowStatus is a textual convention defined in RFC 1443 [10]. It is defined with 6 enumeration:
? active
? notInService
? notReady
? createAndGo
? createAndWait
? destroy
This specification uses RowStatus in every read-creatable table.
4.MIB-II and other MIB support
All SNMP agents supporting LAN Emulation Servers may implement MIB II, and are also encouraged to implement RFC 1695. This chapter explains how ELAN MIB, LES MIB and BUS MIB are related to each of these MIB modules.
4.1MIB II support
LAN Emulation Servers present no interfaces as defined in MIB II. They are however related to one or more ATM interfaces in many ways though:
? LECS can be listening to one or more ATM interfaces with a well-known ATM address as defined in the LANE Specification.
? LES can be receiving/sending control or ATM Le-ARP traffic via one or more ATM interfaces.
? BUS can be receiving/forwarding traffic on one or more ATM interfaces.
The ATM interface is specified throughout the MIB modules where Virtual Circuits in use by servers are defined. It is also specified in every server configuration table where the server’s ATM addresses are defined. The latter is provided to enable network managers to determine which ATM switch the servers derived their ATM addresses from.
4.2AToMMIB Support
LAN Emulation Servers use Virtual Circuits (Switched or Permanent) to communicate with the Clients. Full information on the VCCs is found in the AToMMIB. LAN Emulation Servers MIB provide the indexing for these VCCs so network managers can obtain the attributes of a server VCC from the AToMMIB.
PVCs (Permanent Virtual Circuits) are created by the network manager in the AToMMIB. LAN Server MIBs provide writable objects so the network manager can use the PVCs created in the AToMMIB. (i.e. the lesVccTable and busVccTable)..
5.Emulated LAN MIB Description
5.1Management model
This specification defines three MIB modules: ELAN MIB, LES MIB and BUS MIB. The ELAN MIB provides network manager with the means to change the configuration of ELANs. The LES and BUS MIBs allow reading back of the current status of the ELANs. This chapter describes ELAN MIB.
It is important to understand that the ELAN MIB only manages a repository of static information. To create an ELAN which a client can join will actually require three stages using these MIBs:? create a new ELAN in the ELAN MIB
? create a LES for that ELAN using the LES MIB
? create a BUS for that ELAN using the BUS MIB
These operations must be performed in these separate MIBs because there is no guarantee that any of the components in question will be collocated. Indeed while a LES and BUS may be likely to be managed by a single agent, it is highly likely that the user of information in the ELAN MIB (e.g. an LECS) will not be collocated with the LES or BUS. The LANE specification currently provides no standard method for centralised creation of LE Servers, hence the three operations required to create an ELAN.
The ELAN MIB simply deals with information that will be required to enable a client to join an ELAN. This information can be divided into two types: information required to decide which ELAN a client should join and information which a client will need to join the ELAN.
The assignment of clients to ELANs is controlled using ‘policies’. A policy is a rule based on information available on a client (such as ATM address, ELAN type etc.) linking that client to an ELAN. These are described in detail later in this chapter.
Typically the information in this MIB would be used by an LECS, the former in deciding which ELAN, if any, a client should be assigned to on the basis of its CONFIG_REQUEST, and the latter in deciding what to put in a CONFIG_RESPONSE. It is possible for an ELAN to exist without an LECS however, with a client obtaining this information by some other means. While such means are outside the LANE specification and therefore outside the scope of this document, it was the intention not to preclude such implementations. This is why the LECS portion of the ELAN MIB is a separate group, allowing the ELAN MIB to exist without requiring an LECS.
Systems which implements the LECS must implement the LECS group , to allow the LECS to be monitored and controlled. TLV information also resides in this part of the MIB since this is specific to the LECS configuration mechanism.
While the topology of ELANs can be controlled using the ELAN MIB, by determining which ELANs and LESs clients will use, this MIB does not reflect the current topology. To determine the current topology of an ELAN (which clients are attached to which LESs and BUSs) the LES MIB [2] and BUS MIB [3] (and the LEC MIB [1] if detailed information on the client is required) must be used.
The design goal is to decouple the configured and actual ELAN topology to achieve maximum flexibility in LEC assignment and also future LNNI (LAN Emulation Server to Server Protocol) support.
5.2MIB Groups
This section briefly describes each group and object in the ELAN MIB. For more detail consult the MIB definition and the LANE Emulation specification [1.
5.2.1ELAN Administration Group
This group provides a registry for the LEC assignment policy types. There are six LEC assignment policies defined in this group:
? byAtmAddr - assign a LEC to an ELAN by it’s ATM address
? byMacAddr - assign a LEC to an ELAN by it’s MAC address
? byRouteDescriptor - assign a LEC to an ELAN by it’s Route Descriptor
? byLanType - assign a LEC to an ELAN by it’s LAN type, i.e. ieee802.3 or ieee802.5
? byPktSize - assign a LEC to an ELAN by it’s DataFrameSize
? byElanName - assign a LEC to an ELAN by its ELAN name
This table represents the set of assignment policy types which may be supported by the standard implementations of MIBs. These are based on the information available in a typical CONFIG REQUEST. Vendors wishing to create new policies should not extend this table, but instead should define similar tables or objects in their own MIBs. Policy types are defined as OIDs (AutonomousType) to allow vendors to implement their own policies without needing centralised administration of policy types. This table may be extended in the future revisions of the ELAN MIB.
5.2.2ELAN Configuration Group
This group provides configuration information for Emulated LANs. An ELAN is constructed or destroyed in this group for configuration purposes only; an ELAN can be created and many LECs can be assigned to this ELAN (by policies), but this MIB would not reflect whether or not LECs have actually joined the ELAN. The network manager has to poll the individual LECs or the LES/BUS to determine the actual ELAN topology.
For example, consider an ELAN ‘red’ in the ELAN Configuration table, where the LEC with the ATM address ‘xxx...redx’ is assigned to the ‘red’ ELAN in the LEC assignment by ATM address table. In other words, the LEC ‘xxx...redx’ is configured to ELAN ‘red’ in the ELAN MIB. The LES with the ATM address ‘yyy...redy’ is one of the servers which serves the ELAN ‘red’ as defined in the ELAN MIB’s LES table.
In order to determine whether the LEC ‘xxx...redx’ has actually joined the ELAN ‘red’, or joined the LES ‘yyy...redy’, the network manager must either read the LEC-to-LES information in the LES MIB from the agent of LES ‘yyy...redy’ or talk to the agent of the LEC ‘xxx...redx’ to obtain the LES information from the LEC MIB. In either case, the network manager can match the information from the LES ‘yyy...redy’ or LEC ‘xxx...redx’ to the LEC assignment table by ATM address or the LES table.
In the case where assignment policies are more broad, (e.g. a policy could assign all clients with LanType ‘iee802.5’ to the ELAN ‘Token-Ring’, or address masks might be used so that all clients with a certain ATM address prefix are directed to a particular ELAN) there will be no complete list of clients in the ELAN MIB. In this case a network manager would have to use the LES MIB to find a real list of clients.
In conclusion, the ELAN group provides statically configured information and the LES and LEC MIBs provide the dynamic status information for the Emulated LAN.
5.2.2.1ELAN Configuration Table
elanConfTable lists all Emulated LANs on which this agent maintains information; the elanConfIndex object, an arbitrary integer used as an index in this table, is used elsewhere in the ELAN MIB to identify a particular ELAN. Emulated LANs should be created or destroyed from this table in conjunction with operations to create or destroy the related service components as described in section 5.1. This table can be used by the entity which assigns a LAN Emulation clients to ELANs. This might be a LAN Emulation
Configuration Server (LECS), or in an environment where there is no LECS, the information might be used directly by a system to configure LAN Emulation Clients (LECs).
A network manager can construct the ELAN configuration table as well as the LEC assignment table locally. And then configures the LEC according to the configuration through the LEC MI
B defined in [6]. The table contains the ELAN’s name, LAN type, maximum frame size, and also has a TLV selector to enable it to choose a set of TLV-defined properties (set to zero if the LECS group is not supported).
5.2.2.2ELAN LES table
This table lists all LES associated with ELANs managed by the agent. Only the ATM address of the LES is held, and because the LANE specification permits multiple LES addresses per ELAN, there may be more than one LES per ELAN. All LEC assignment tables are indexed by both the ELAN (elanConfIndex) and LES index (elanLesIndex) to allow the selection of a specific LES address for any client within an ELAN.
5.2.2.3ELAN Policy Table
Throughout this section, all terms are used and they are: ‘accept’ meaning the policy accepts the client (the client has the matching information of the correct type), ‘rejected’ meaning the policy rejects the client (the client didn’t have the information or the information doesn’t match), and ‘failed’ meaning the client was not assigned to any ELAN as the results of the execution of all the policies.
This table describes policies currently in use for assigning LECs to particular ELANs and LESs. These policies will be carried out by whatever entity is using this information, typically an LECS but not necessarily.
When a LECS is supported, the LECS assigns a client to an ELAN based on the information given in the CONFIG request. Information in the CONFIG request is checked against the various policy tables in the ELAN MIB.
There can be multiple policies used in determining the LEC assignment at one time. These policies are executed in order of their priorities, with the lowest number getting the highest priority. (A policy with priority of 1 would be executed first.) Conflicts between policies may occur but the LECS behavior is implementation dependent.
If there exist multiple policies of the same priority, they are executed at the same time, and all policies must succeed.
Policies are grouped with the elanPolicySelectorIndex. This allows disjoint policy sets to be created which allows individual LECSs (or other users of this data) to use different policies.
Users of the information in the policy and assignment tables should use the following procedure when attempting to assign clients:
Find the first policy with the highest priority level with the appropriate PolicySelectorIndex.
Check to see if the client matches any assignments for this policy type. For the standard policies this will involve looking up in an assignment table (e.g. for elanPolicyType of byAtmAddr, the
elanLecAtmAddrTable must be consulted). If the client passes, there will be one or more
ELAN/LES index pairs. If the client fails to find any appropriate ELAN/LES pair with this policy, it has failed, and must restart from the next priority down. If there are no policies with a lower
priority than the current one, then the client is not assigned to any ELAN and has been rejected.
If there are more policies with the same priority level as the one which just passed, these must also be evaluated as described above.
If a client has passed all the policies with a particular priority level, there will have been at least one ELAN/LES pair generated per priority. If no pair is common to every policy (i.e. the client passed
every policy, but the policies failed to agree on any ELAN/LES pair) then the client has failed for this priority level, and behaviour is as if the client had failed against any one of the policies at this priority. If a single ELAN/LES pair can be identified as common to the results of all the policies, then this is taken as the final result. If there are multiple matches and the client could be assigned validly to more than one ELAN/LES, any may be chosen, the particular outcome being
implementation defined.
An example configuration might consist of four ELANs: TRed, TBlue, ERed and EBlue. Clients with an ATM address prefix of rrrrrrrrrrrrrrr would be assigned to the Red ELANs, TRed if they are Token-ring clients and ERed if they are Ethernet clients. Otherwise they get assigned to TBlue or EBlue again according to LAN type. This would require three ElanPolicyEntries, at two priority levels. There would be two entries at priority level one: a policy of type byAtmAddr and a policy of type byLanType. There would be one entry at priority level two: byLanType. The assignment by ATM address table would contain two entries, both with an ATM address beginning with rrrrrrrrrrrrrrr and an address mask with only the relevant prefix bits set, one pointing to TRed and an appropriate LES index, the other pointing to ERed with an appropriate LES index. As for the byLanType, the object elanConfLanType in the elanConfTable is used. If the client’s requesting LAN type is Ethernet, then the first elanConfEntry that has the elanConfLanType set to aflane8023(2) and it also matches the ATM prefix is the ELAN this client is assigned to.
If there is no data available on the client for a policy, then that policy would fail. The client is rejected by that policy.
The agent should refuse to create any policy it does not support.
5.2.2.4LEC assignment table by ATM address
This table is indexed by the ELAN index which points to the ELAN this LEC belongs to, the particular LES within that ELAN it will be sent to, and the ATM address plus mask of the LEC. The ATM mask allows the network manager to specify portions of an ATM address. A client would be matched by an assignment entry if bits in its address corresponding to non-zero bits in the mask match the address in the table.
5.2.2.5LEC assignment table by MAC address
This table is indexed by the ELAN index, LES index within the ELAN, and the MAC address (with mask) of the LEC. The MAC address is compared with the client’s when executing byMacAddress policies.
5.2.2.6LEC assignment table by Route Descriptor
This table is indexed by the ELAN index, the LES within the ELAN, and the Route Descriptor of the LEC, which consists of a segment id and a bridge number. The route descriptor is compared with the client’s when executing byRouteDescriptor policies.
5.2.3LECS Configuration Group
This enables network managers to configure and monitor LECSs. It also provides configuration information on TLV (type, length and value ) entries to be used in CONFIG responses..
5.2.3.1LECS Configuration table
This table contains the configuration and status information for all LECS managed by this agent. This table is used to create, delete or configure a LECS. Critical objects such as the lecsAtmIfIndex, lecsAtmAddrSpec, and lecsAtmAddrMask cannot be modified unless the lecsAdminStatus is set to down(2). That is, the network manager has to bring the LECS down to in order to change a LECS’s ATM address or ATM interface value. These changes can be brought into effect by setting the lecsAdminStatus to up(1). The object lecsAtmIfIndex provides the number of the ATM interface on which the LECS is listening for CONFIGURE requests. This value must match an existing value in the ifTable. This object is set to zero when the ATM interface is not specified or there is more than one ATM interface used by the LECS.
A network manager may instruct the LECS to attempt to register and listen on a particular address. This is achieved through use of the lecsAtmAddrSpec and lecsAtmAddrMask objects. The default values for these objects will cause a LECS to use the with a well-known ATM address (reference to LANE 1.0 specification section 5.2.1.2 ). Clearly if more than one LECS is created on any interface (or on multiple interfaces which would share the domain of the well known address) at least one of them should use some other address.
To enable different LECSs to enact different sets of policies, a policy selector index is set for each LECS.
5.2.3.2TLV table
This table is used to configure TLVs (Type, Length, and Value) for each ELAN. The table is indexed by a selector index, the TLV tag and an index. The selector allows multiple TLVs to be grouped together, so different ELANs can use different sets of TLVs. The index allows multiple TLVs with the same tag but different values
Network manager can create TLVs and assign them to an ELAN by specifying corresponding selector indices in both the TLV table and the elanConfTable.
5.2.3.3VCC table
This table contains the LE CONFIG VCCs from all LECs to the LECS. This table can be used by the network manager as the central place for tracing VCCs.
5.2.4LECS Statistics Group
In addition to the LECS fault management group, the LECS statistics group also provides per LECS error counters.
5.3.4.1LECS statistics table
This table lists all counters associated with the LECS this agent maintains.
5.2.5LECS Fault Management Group
This group provides fault information for LECSs. The network manager can enable or disable the error logging capability of a LECS. The enabled LECS will log the error events until the maximum number error log entry is reached.
The logged events are saved in the LECS Error Log table.
5.2.5.41LECS Error Log Control Table
This table is used to control error logging capability on a LECS. The network manager can enable/disable error logging of a particular LECS managed by the agent. It can also reset the error log of a LECS. The LECS must clear all the error log entries upon such a request.
The object lecsErrCtlMaxEntries describes the maximum number of errors a LECS can log. If this object is one, the LECS can only save the last error event. It is a read only object. The object lecsErrCtlLastEntry gives a pointer to the last error log saved by a LECS in the lecsErrLogTable. It can be used by the network manager to read the most recent entry.
5.2.5.2LECS Error Log Table
This table contains all the error logs maintained by the LECSs managed by the agent. Each entry describes when the error occurred, the nature of the error and the ATM address of the client whose CONFIG request resulted in the error.
The lecsErrLogIndex ranges from 2 to 32 minus 1 down to 1. It is assigned consecutively in the descending order. The network manager can easily retrieve the most recent N entries by using the get-next on the value of this object. The entries after 1 are discarded. For example, if the lecsErrCtlMaxEntries is 5, and the LECS has received 2 to 32 minus 1 minus 100 entries so far. The values of the lecsErrLogIndex for this LECS in the lecsErrLogTable are 100, 99, 98, 97 and 96 with the entry 96 being the most recent error occurred.
https://www.doczj.com/doc/6b10143884.html,N Emulation Server MIB Description
This MIB provides LES management information. The implementation of this MIB is mandatory for agents managing LESs.
6.1Management model
The LES management model is designed to be compliant with the LAN Emulation 1.0 specification. It was also intended to facilitate the accommodation of future LAN Emulation Server to server protocol management extensions.
This MIB may be used to determine the distribution of the LECs among LESs, and to create, configure and monitor LESs.
6.2MIB Organisation
The MIB is divided into four groups: the LES Configuration group which provides configuration and topology information; the LES Statistics Group which provides various counters for each LES; the LES-LEC Statistics group which provides per LES/LEC pair counters; the LES Fault management group which logs LES error information.
6.3MIB Groups
6.3.1LES Configuration Group
6.3.1.1LES Configuration table
This table lists all LAN Emulation Servers managed by this agent.
The object lesAtmAddrSpec specifies an ATM address that, with the ATM address mask, determines a portion of the ATM address that the LES on the designated ATM interface will use to derive the actual ATM address from the network or ILMI. The derived ATM address is specified in the object lesAtmAddrActual, which is used to receive ATM ARP requests.
The object lesElanName gives the name of the Emulated LAN this LES is providing service for. This object may be used to identify the ELAN the LES is in.
The object lesLanType describes the type of the ATM Emulated LAN this LES is providing service to. If the LEC has specified a LAN type in its JOIN request that does not match with the value of this object, the LES will reject the request. Only 802.3 and 802.5 LAN types are supported.
6.3.1.2LES VCC Table
This table lists all the Control Distribute VCCs used by the LES to distribute control traffic to the participating LECs. The Control Distribute VCC can either be point-to-point or point-to-multipoint calls. This table is read only if SVCs are used and writable if PVCs are used.
Each entry indicates the ATM interface number, VPI value and VCI value, which comprise the index to the atmVclTable in the AToMMIB.
6.3.1.3LES ARP table by MAC address
This table provides access to an ATM LAN Emulation Server’s MAC-to-ATM address table.. It contains entries for unicast addresses and the broadcast address.
An entry for the broadcast MAC address will have the ATM address of a BUS. When the entry is for a unicast MAC address the corresponding ATM address will be for a LEC.
6.3.1.4LES ARP table by Route Descriptor
This table provides access to an ATM LAN Emulation Server’s RouteDescriptor-to-ATM ARP cache. The entries in this table are set-up by the agent or network manager depending on the entry type.
The Route Descriptors are presented as Segment Id (ring number) and Bridge number.
6.3.1.5LES-LEC topology table
This table lists all LAN Emulation clients serviced by LESs specified in the lesConfTable. This table can be used to retrieve the topology of an ELAN, i.e. the LES to LECs mapping information.
An entry in this table is created by the agent when a LEC registers successfully with the LES. The lesLecCtlDirectVpi and lesLecCtlDirectVci objects can be modified by the network manager if PVC is used.
6.3.2LES Statistics Group
This table contains all counters the LESs maintain. This table augments the lesConfTable. It provides performance and fault counters on a per LES basis.
The table lists all error types listed in the Table 13 in “ATM Forum LAN Emulation Over ATM Specification, V1.0”.
6.3.3LES-LEC Statistics Group
This table contains all LE-ARP request related counters and error counts on a per LEC-LES pair basis.
6.3.4LES Fault Management Group
This group provides fault management information for managing a LES. The network manager can enable/disable the error logging capability of a LES. The enabled LES will log the error event until the maximum number error log entry is reached.
The logged events are saved in the LES Error Log table.
6.3.4.1LES Error Log Control Table
This table is used to control the error logging capability of a LES. The network manager may enable or disable error logging on a particular LES managed by the agent. It can also reset the error log of a LES. The object lesErrCtlMaxEntries describes the maximum number of errors a LES can log. If this object is one, the LES will only save the last error event. The object lesErrCtlLastEntry gives a pointer to the last error log saved by a LES in the lesErrLogTable.
6.3.4.2LEC Error Log Table
This table contains all the error logs maintained by the LESs managed by the same agent. Each entry describes the error occurred, the nature of the error and the ATM address of the client whose request that resulted in the error.
The lesErrLogIndex ranges from 2 to 32 minus 1 to 1. It is assigned consecutively in the descending order. The network manager can easily retrieve the most recent N entries by using the get-next on the value of this object. The entries after 1 are discarded. For example, if the lesErrCtlMaxEntries is 5, and the LES has received 100 entries so far. The values of the lesErrLogIndex for this LES in the lesErrLogTable are 100, 99, 98, 97 and 96 with the entry 100 being the most recent error occurred.
7.Broadcast and Unknown Server MIB description
7.1Management model
This MIB enables network managers to create, destroy, configure and determine the current status of BUSs and topology of the portions of ELANs being served by BUSs.
7.2MIB Organisation
The MIB is devided into two groups: BUS Configuration group which provides BUS topology information. And BUS Fault Management group which provides BUS statistics and BUS-LEC statistics.
7.3MIB Groups
7.3.1BUS Configuration Group
This group includes the object busNextId, BUS Configuration table, BUS VCC table and BUS-LEC topology table.
The object busNextId provides the network manager the next available index used to create a BUS.
7.3.1.1BUS Configuration Table
This table lists all LAN Emulation Broadcast and Unknown Servers (BUS) this agent manages. The BUS handles data sent by an LE Client to the broadcast MAC address, all multicast traffic, and initial unicast frames which are sent by a LEC before the appropriate data direct target ATM address has been resolved. There can be multiple BUSs per ELAN, but a BUS can service only one ELAN.
7.3.1.2BUS VCC Table
This table lists all the Multicast Forward VCCs used by the BUS to forward multicast traffic to the participating LECs. Multicast Forward VCCs can either be point-to-point or point-to-multipoint. This table is read only if SVCs are used and writable if PVCs are used.
7.3.1.3BUS-LEC Topology Table
This table lists the actual LECs being serviced by the BUS. It can be used to determine the mapping between BUSs and LECs.
This table provides information for Multicast send VCCs between BUS and LE clients. Objects busLecMcastSendAtmIfIndex, busLecMcastSendVpi and busLecMcstSendVci can only be modified if PVC is used.
7.3.2BUS Statistics Group
3DLO 3D long offset seismic survey三维长偏移距野外资料采集 3DHR-HR 3D High resolution –high ???seismic survey 三维高分辨－高密野外资料采集。AAC = adjusted AC; ABI inclination at the drill bit AC acoustic 声波时差 ACN =adjusted CN; ADN Azimuthal neotron density AIT* Array Induction Imager Tool A&S admistration&service AHC Ascendant Hierarchical Clustering ARC Induction Resistivity GR annulus pressure ingrated tool ARI Azimuth resistivity imager方位电阻率成像测井仪 APD Elevation of Depth Reference (LMF) above Permanent Datum APWD apparatus whle drilling ASI Array seismic imager阵列地震成像仪 A VG: Average A VO Amplitude Versus Offset(Amplitude variation with offset calibration)振幅-炮检距 关系 AZI: Azimuth (deg) BBC Buy Back Contract BGG: Background Gas (%) BGP 物探局 BHFP bottomhole flowing pressure BHS :Borehole Status BHT :Bottom Hole Temperature BHTA 声波幅度 BHTT 声波返回时间 BLWH Blue White BML below mud line BOP Blow out preventer BOP stack 防喷器组 BS Bit Size BSW basic?? saturation water(综合含水) CAL borehole diameter 井径 CAST 声波扫描成像测井仪 CBI Central Bank of Iran CBIL 井周声波成像 CBL Cement Bond Log CC correlation coefficient CCAL common core analysis常规岩心分析 CCL Casing Collar Locator CCM Contractors Committee Meeting CDF cumulative density function CDF Calibrated Downhole Force
EVT(Engineering Verification Test)工程验证测试阶段 DVT(Design Verification Test)设计验证测试阶段 DMT（Design Maturity Test）成熟度验证 MVT（Mass-Production Verification Test）量产验证测试 PVT(Production/Process Verification Test)生产/制程验证测试阶段MP(Mass Production)量产 工程师类: PE: Product Engineer 产品工程师 Process Engineer 制程工程师 ME: Mechanical Engineer 机构工程师 IE：Industrial Engineer 工业工程师 QE: Quality Engineer 品质工程师 SQESupplier Quality Engineer供货商质量工程师 QC quality control 品质管理人员 FQC final quality control 终点质量管理人员 IPQC in process quality control 制程中的质量管理人员 OQC output quality control 最终出货质量管理人员
IQC incoming quality control 进料质量管理人员TQC total quality control 全面质量管理 POC passage quality control 段检人员 QA quality assurance 质量保证人员 OQA output quality assurance 出货质量保证人员 QE quality engineering 品质工程人员 TE Test Engineer 测试工程师 AE Automatic Engineer 自动化工程师 研发类: R&D Research & Design 设计开发部 ID (Industry Design)工业设计 MD (Mechanical Design)结构设计 HW(Hardware) 硬件设计 SW(Software)软件设计 PDM Product Data Management 产品数据管理 PLM product lifecycle management 产品生命周期管理电子设计:
微课以小见大的写作手法 今天我们一起来学习以小见大的写作手法。第一步我们要明确什么是以小见大？ （提问）某某同学，你对这四个字有什么了解？ 很好！首先从字面意思上看，以小见大是一个四字成语：以者，用也；见者，表现也。顾名思义，它的解释就是用小的表现大的。指通过小事可以看出道理，通过部分可以看出整体，那么作为一种写作手法，我们又要怎么去定义它呢？ 以小见大法，也称小中见大法，即文章作品中，通过小事件和细节来揭示重大主题写作方法。我们要抓住关键字来理解，这句话的关键字就是小事件细节和重大主题，分别是小和大的指代。 这种写作手法有哪些特点呢？ 从材料上来讲：在于抓住一事一物、一情一景；“以小见大”的基本点在于小，一事一物，一情一景都是小的选取对象。 从写法上来讲：从大处着眼、小处落笔；关键在于立意要高，要大，但要注意的是要在尽可能微小之处来体现立意的高大。 从表达效果上来讲：深入发掘，展开联想，为读者创造一个比现实生活更为广阔、更为深远的艺术境界。 （提问）那么有哪些文章用了“以小见大”的写作手法呢？某某同学，你来给大家简要介绍一下？（参考答案：鲁迅的很多作品都用了以小见大的手法，比如《药》就是通过写夏瑜的命运来写整个社会的悲惨命运。） 很好！其实这种写法在文章中比较常见。接下来我们具体来看看几个运用了“以小见大”手法的比较典型的例子： 说到“以小见大”的文章，大家可能第一想到的就是鲁迅先生的《一件小事》，《一件小事》是“以小见大”手法运用的一个典范，描写的是鲁迅出外搭乘人力车，人力车夫在本不用负责的情况下搀扶起被撞倒的老妇人，并将其送至警署的这么一件小事。这篇文章在选材上十分简单，就是日常生活中的一件极其平凡的小事，但从这么一件小事里却折射出了一个“下等人”的高尚的人格力量，这篇文章短小精悍，全文仅一千字左右，但却震撼了人们的心灵。 还有一个很典型的例子是巴金老人的《小狗包弟》，这篇文章选自《随想录》，作者通过描写一条小狗的故事来反映文革的现实，连一条小狗都不能逃过劫难，体现了在“文革”时代任何生命都不能免受侵害的现实。 这两篇文章都运用了“以小见大”的写作手法，而且都运用得非常成功，对小材料的细节描写激发了作者的真情实感，使得文章真实而且感人，达到了很好的效果。 那么以上两篇文章为例，我们来分析一下使用“以小见大”手法的好处？ （提问）同学们先来谈谈吧，某某同学，你是怎么看的？还有人补充吗？ 好，现在我们一起来总结一下： 1、这种艺术处理以一点观全面，给写作者带来了很大的灵活性和无限的表现力； （比如《一件小事》中作者只描写了一位人力车夫的故事，却能将其延伸到整个下层人民甚至整个社会，作者可以极尽表达自己的思想和情感） 2、为读者提供了广阔的想象空间，能产生丰富的联想；（比如从《小狗包弟》 中读者直接获得的情感体验是作者对包弟的歉疚和忏悔，但读者可以思考这份忏悔是否只是对包弟，忏悔又具有怎样的现实意义等，读者想象的空间很大）
生产制造企业英文及缩写大全 企业生产经营相关英文及缩写之(1)--供应链/物料控制.............. 企业生产经营相关英文及缩写之(2)--生产/货仓.................... 企业生产经营相关英文及缩写之(3)--工程/工序（制程）............ 企业生产经营相关英文及缩写之(4)--质量/体系.................... 业生产经营相关英文及缩写之(5)--营业/采购...................... 企业生产经营相关英文及缩写之(6)--BOM 通用缩写............... 企业生产经营相关英文及缩写之(7)--Shipping 装运.............. 企业生产经营相关英文及缩写之(8)--协议/合同/海关 .............. 企业生产经营相关英文及缩写之(9)--称号/部门/公司 .............. 企业生产经营相关英文及缩写之(10)--认证/产品测试/标准......... 企业生产经营相关英文及缩写之(11)--Genenic 普通书写.......... 企业生产经营相关英文及缩写之(12)--Currencies 货币代码.......
企业生产经营相关英文及缩写之(1)--供应链/物料控制 Supply Chain 供应链? / Material Control 物料控制 APS Advanced Planning Scheduling 先进规划与排期 ATO Assembly To Order 装配式生产 COM Customer Order Management 客户订单管理 CRP Capacity Requirement Planning 产量需求计划 EMS Equipment Management System / Electronic Management Syste m 设备管理系统/ 电子管理系统 ERP Enterprise Resource Planning 企业资源规划 I/T Inventory Turn 存货周转率 JIT Just In Time 刚好及时- 实施零库存管理 MBP Master Build Plan 大日程计划-主要的生产排期 MES Management Execution System 管理执行系统 MFL Material Follow-up List 物料跟进清单 MMS Material Management System 物料管理系统 MPS Master Production Scheduling 大日程计划-主要的生产排期MRP Material Requirement Planning 物料需求计划 MS Master Scheduling 大日程计划-主要的生产排期 MTO Make To Order 订单式生产 MTS Make To Stock 计划式生产 OHI On Hand Inventory 在手库存量 PSS Production Scheduling System 生产排期系统 SML Shortage Material List 缺料物料单 VMI Vendor Managed Inventory 供应商管理的库存货 UML Urgent Material List 急需物料单
1. info:site_name 这个修饰语可以返回关于某特定页面的信息. 2. 同样的,在普通搜索后点击‖相似网页‖可以链接到Google认为相似的页面结果. 3. 如果只想搜索某一个风址里的内容,可能用site: 来实现,比如说search tips site:https://www.doczj.com/doc/6b10143884.html,. 4. 上述技巧通过像https://www.doczj.com/doc/6b10143884.html,这样的目录网站并动态地生成网址. 5. 也可直接进入Google Directory这样的人工挑选出来的数量有限的数据库网站,网址是https://www.doczj.com/doc/6b10143884.html,. 6. intitle和inurl这样的布尔运算符像OR一样在Google Directory中同样适用. 7. 当你用Google图片搜索时,用site:的修饰语可以只搜索某一个网站内的图片,比如dvd recorder site:https://www.doczj.com/doc/6b10143884.html,. 8. 同样的,用‖site:.com‖只会返回带有.com域名后缀网站里的结果. 9. Google新闻(https://www.doczj.com/doc/6b10143884.html,)有他自己的布尔运算符.例如―intext‖ 只会从一条新闻的主体内容里查询结果. 10. 在Google新闻里如果你用―source:‖这个运算符,你可以得到特定的新闻存档.比如:heather mills source:daily_mail 11. 通过‖location:‖过滤器你可以等到特定国家的新闻,比如location:uk 12. 同样的Google博客搜索(https://www.doczj.com/doc/6b10143884.html,)也有它自己的句法.你可以搜索某篇日志的标题,比如―inblogtitle:― 13. Google的普通搜索也可以确实也可以得到精确的结果,不如用‖movie:‖ 来寻找电影评论. 14. ―film:‖修饰语效果也一样. 15. 在搜索框里输入上映时间,Google会提示你提交你的邮编,然后Google就会告诉你什么时候什么地方将会有好戏上演. 16. 如果想要一个专门的电影搜索页面,可以去https://www.doczj.com/doc/6b10143884.html,/movies 17. 如果你圈选了―记住地点‖后,下次你查询电影放映时间只需要输入电影名字就够了. 18. Google确实在电影方面的搜索上下了些功夫.比如在搜索框中输入 ―director:<电影名>‖你将得到什么结果?你肯定猜到了吧. 19. 如果想得到演员名单,如需输入―cast:name_of_film‖ 20. 在乐队名、歌曲名或者专辑名前加上―music:‖可以得到相关的音乐信息和评论. 21. 如果你在搜索框里输入―weather London‖便可以得到伦敦最近四天完整的天气预报. 22. Google也内置了词典,在搜索框里用‖define:the_word‖试试. 23. Goolge保存了网站过去的内容.你可以直接搜索某个页面在Google服务器里的缓存,相关句法是―keyword cache:site_url‖ 24. 相应的,直接在搜索框里输入―cache:site_url‖可以直接进入缓存页面. 25. 如果你手边没有计算器,只要记住Google同样内置了这么一个功能.输入―12*15‖然后点击搜索试试. 26. Google的内置计算器不但可以转换尺寸还可以理解自然语言.搜索一下―14 stones in kilos‖ 27. 汇率转换也同样适用,试试―200 pounds in euros‖ 28. 如果你知道某货币的代码,将得到更加可靠的结果,例如‖200 GBR in EUR‖
石油化工英语常用缩写(第一版) 序号缩写英文中文 1 AC Air Conditioning 空气调节装置 2 AGO Atmospheric gas oil 常压瓦斯油 3 AML Approved Manufacturers' List 批准的厂商名单 4 APE Area Project Engineer 区域项目工程师 5 AR Atmospheric residue 常压渣油 6 ARDS Atmospheric residue desulfurization 常压渣油加氢脱硫 7 ASME American Society of Mechanical Engineers 美国机械工程师协会 8 BD Business Director 商务主任 9 BD Business Development 市场部 10 BEDP Basic Design Engineering Package 基础设计包 11 BFW Boiler feed water 锅炉给水 12 BL Battery limits 界区 13 BEDD Basic Engineering Design Data 基础工程设计数据 14 BM Bill of Material 材料表 15 BOD Basis of Design 设计基础 16 BOD Biological Oxygen Demand 化学需氧量 17 BP Boiling point 沸点 18 BS Bright stock 光亮油 19 BSI British Standards Institute 英国标准协会 20 BTEX Benzene, toluene, ethyl benzene, xylene 苯,甲苯,乙苯,二甲苯 21 BTU British thermal unit 英热单位 22 BTX Benzene, toluene, xylene 苯,甲苯,二甲苯 23 C Construction 施工 24 CAD Computer Aided Design 计算机辅助设计 25 CADD Computer Aided Design and Drafting 计算机辅助设计和绘图 26 CCR Conradson carbon residue 康氏残炭 27 CCR Continuous Catalyst Regeneration 催化剂连续再生 28 CDU Crude distillation unit 原油蒸馏装置 29 CGO Coker gas oil 焦化瓦斯油 30 CI Cetane index 十六烷指数 31 CL Center line 中心线 32 CM Construction Manager 施工经理 33 CN Conference Note 会议纪要 34 COD Chemical oxygen demand 化学需氧量 35 CPDP Chinese Preliminary Design Package 中国初步设计包 36 CPM Critical Path Method 关键路径法 37 CR Catalytic Reforming 催化重整 38 CS Carbon Steel 碳钢 39 CW Cooling Water 冷却水 40 FEED Front End Engineering Design 前期工程设计 41 GB GUO BIAO 国标 42 GCD Guaranteed Completion Date 保证完成日期 43 GG Gauge glass 玻璃液面计 44 GHSV Gaseous hourly space velocity 气体体积空速 45 GPH Gas phase hydrogenation 气相加氢 46 GSN Global Supply Network 全球供应网络 47 GTG Gas Turbine Generator 燃气涡轮发电机 48 GW Gross weight 毛重 49 HAZID Hazard Identification Review 危险识别审查 50 HAZOP Hazard and Operability Study 危险与可操作性研究
制造业中常用的英文缩写 工业常用的英文缩写 品质人员名称类 QC quality control 品质管理人员 FQC final quality control 终点质量管理人员 IPQC in process quality control 制程中的质量管理人员 OQC output quality control 最终出货质量管理人员 IQC incoming quality control 进料质量管理人员 TQC total quality control 全面质量管理 POC passage quality control 段检人员 QA quality assurance 质量保证人员 OQA output quality assurance 出货质量保证人员 QE quality engineering 品质工程人员 品质保证类 FAI first article inspection 新品首件检查 FAA first article assurance 首件确认 CP capability index 能力指数媵 CPK capability process index 模具制程能力参数 SSQA standardized supplier quality audit 合格供货商品质评估 FMEA failure model effectiveness analysis 失效模式分析 FQC运作类 AQL Acceptable Quality Level 运作类允收品质水准 S/S Sample size 抽样检验样本大小 ACC Accept 允收 REE Reject 拒收 CR Critical 极严重的 MAJ Major 主要的 MIN Minor 轻微的 Q/R/S Quality/Reliability/Service 品质/可靠度/服务 P/N Part Number 料号藊 L/N Lot Number 批号 AOD Accept On Deviation 特采 UAI Use As It 特采 FPIR First Piece Inspection Report 首件检查报告 PPM Percent Per Million 百万分之一 制程统计品管专类 SPC Statistical Process Control 统计制程管制 SQC Statistical Quality Control 统计质量管理 GRR Gauge Reproductiveness & Repeatability 量具之再制性及重测性判断量可靠与否DIM Dimension 尺寸 DIA Diameter 直径 N Number 样品数
以小见大的亲情作文优秀3篇 以小见大的亲情作文（一）： 生活中有许多感人的事，它们像海底的一颗颗珍珠，珍藏在我们心中！ 一个阳光明媚的早晨，院子尽是小鸟清脆的歌声――我该去上学了！ 爸爸推着自行车，我坐在后座准备带我去上学，正在跟妈妈描述昨晚做梦时的情形，并且用手比划着，爸爸什么也不知，只顾着往前走，就在准备要过门槛的那一刻，意外发生了。自行车往前一拱，顿时我身子倾斜，两手不知所措“蹼蹬”一声，我重重的摔倒在地。地下满是尖尖的石头，我的头流淌着鲜血，失声痛哭起来，这声足能够震动山岗。爸妈一看这情形着急起来，爸爸立刻抱起我，飞奔向医院，一边跑一边安慰我但是，不知是谁惹怒了雨神，突然下起蒙蒙细雨，随着时间一分一秒的过去，下起了倾蓬大雨，路上的行人见状纷纷回家，这时爸爸皱起了眉头，不管下着多大的雨，不管路地有多么滑，爸爸都紧紧地抱着我，大步向医院奔去，最后到医院了，爸妈的衣服全湿透了，而我却是浓浓的暖意，感动地泪水夺眶而出。 爸妈我爱您们！ 以小见大的亲情作文（二）： 以小见大的亲情 父亲也真搞笑，老远的给我送月饼来，还有两个梨和一小撮茶叶，这些东西加起来也不到车费的三分之一呢。
和同学们瓜分了月饼和梨，那一小撮茶叶却弄丢了。或许是当垃圾给扫掉了吧。我一翻垃圾篮，果然在那，幸好有袋子装着。 我把那茶叶倒进开水中，刚好能泡上一杯浓浓的茶。就是这杯浓热的茶，使我又一次不能入眠。一整个下午，我就静静地想着过去的事。 我们村子里的人除了待客和供神鬼，自我是很少喝茶的，连开水也难得喝上一口。渴了就舀上一大碗带点粥的米汤咕噜咕噜地灌下去。只有我们家，四姐弟都喜欢喝茶，而我母亲向来是不主张我们喝茶的，在她眼里喝茶跟喝药一个样，只是在吃多了油腻的东西的才特许我们喝上一两杯。但我们喝得多了，她也就不怎样管我们了，只是她还是一口也不喝，除非拉肚子。说来好笑，我母亲认为浓茶是能够治拉肚子的，我小时候就十分信奉这种说法。肚子不舒服了就偷一把茶叶塞进嘴里，用口水慢慢地将它泡软，然后就咀嚼起来，有时连渣也全吞了下去。虽然有点苦，但为了肚子，我那时就很勇敢，况且吃完后很长一段时间口中还甘甜甘甜的。我很喜欢那种感觉。也真是奇怪，那方法每次都灵验。我曾把这方法传授给别的小孩子，但他们都爱不了那苦。 我渐渐长大，再也不吃茶叶了，却还是喜欢喝茶，个性是早上起来，先泡上一杯浓茶再去刷牙洗脸运动，回来时那茶已差不多泡好了。捧上一本小说边喝边看，那真是人生一大快事。 这样的快事在学校里是享受不到的。因为学校里太热闹，生活节
石油化工英语常用缩写(第一版)(https://www.doczj.com/doc/6b10143884.html,石油软件下载) 序号缩写英文中文 1 AC Air Conditioning 空气调节装置 2 AGO Atmospheric gas oil 常压瓦斯油 3 AML Approved Manufacturers' List 批准的厂商名单 4 APE Area Project Engineer 区域项目工程师 5 AR Atmospheric residue 常压渣油 6 ARDS Atmospheric residue desulfurization 常压渣油加氢脱硫 7 ASME American Society of Mechanical Engineers 美国机械工程师协会 8 BD Business Director 商务主任 9 BD Business Development 市场部 10 BEDP Basic Design Engineering Package 基础设计包 11 BFW Boiler feed water 锅炉给水 12 BL Battery limits 界区 13 BEDD Basic Engineering Design Data 基础工程设计数据 14 BM Bill of Material 材料表 15 BOD Basis of Design 设计基础 16 BOD Biological Oxygen Demand 化学需氧量 17 BP Boiling point 沸点 18 BS Bright stock 光亮油 19 BSI British Standards Institute 英国标准协会 20 BTEX Benzene, toluene, ethyl benzene, xylene 苯,甲苯,乙苯,二甲苯 21 BTU British thermal unit 英热单位 22 BTX Benzene, toluene, xylene 苯,甲苯,二甲苯 23 C Construction 施工 24 CAD Computer Aided Design 计算机辅助设计 25 CADD Computer Aided Design and Drafting 计算机辅助设计和绘图 26 CCR Conradson carbon residue 康氏残炭 27 CCR Continuous Catalyst Regeneration 催化剂连续再生 28 CDU Crude distillation unit 原油蒸馏装置 29 CGO Coker gas oil 焦化瓦斯油 30 CI Cetane index 十六烷指数 31 CL Center line 中心线 32 CM Construction Manager 施工经理 33 CN Conference Note 会议纪要 34 COD Chemical oxygen demand 化学需氧量 35 CPDP Chinese Preliminary Design Package 中国初步设计包 36 CPM Critical Path Method 关键路径法 37 CR Catalytic Reforming 催化重整 38 CS Carbon Steel 碳钢 39 CW Cooling Water 冷却水 40 FEED Front End Engineering Design 前期工程设计 41 GB GUO BIAO 国标 42 GCD Guaranteed Completion Date 保证完成日期
一:常用術語 Hon Hai 鴻海 CMM Component module move 機動元件整合 CEM Contract Manu faction service 合約委托代工 IBSC Internet Business Solution Center 國際互聯網應用中心 PCEG Personal Computer Enclosure group 個人電腦外設事業群（FOXTEQ）CCBG Connector& cable business group CPBG Competition business group ESBG Enterprise system business group 鴻富錦事業群 SABG system assembly business group 系統組裝事業群 NWE Net Work Enclosure NSE Network system enclosure NSG Network system group NFE Network flexible enclosure Foxcavity = HZ = Hong Zhun 鴻準 Stamping tool shop I 沖模一廠 Stamping tool shop II 沖模二廠 Prototype workshop 樣品中心 Steel factory 裁剪廠 PCE molding tooling workshop PCE塑模廠 Hua Nan test and measurement center 華南檢測中心 MPE mobile phone enclosure MPE MBE mobile phone and notebook enclosure 明塑厂 MGE Alloy magnesium alloy enclosure 鎂合金 Engineer standard 工標 Document center (database center)資料中心 Design Center 設計中心 Painting 烤漆(廠) Assembly組裝(廠) Stamping 沖壓(廠) Education and Training教育訓練 proposal improvement/creative suggestion提案改善 Technological exchange and study 技術交流研習會 Technology and Development Committee 技術發展委員會 BS Brain Storming 腦力激蕩 QCC Quality Control Circle 品質圈 PDCA Plan Do Check Action 計劃執行檢查總結 DCC delivery control center 交貨管制中心 3C Computer 電腦類產品 Consumer electronics 消費性電子產品 Communication 通訊類產品 Core value（核心价值） Love 愛心
3DLO 3DHR-HR 3D long offset seismic survey 三维长偏移距野外资料采集 3D High resolution–high ???seismic survey三维高分辨－高密野外资料采集。 AAC = adjusted AC; ABI inclination at the drill bit AC ACN ADN AIT* A&S AHC ARC ARI acoustic 声波时差 =adjusted CN; Azimuthal neotron density Array Induction Imager Tool admistration&service Ascendant Hierarchical Clustering Induction Resistivity GR annulus pressure ingrated tool Azimuth resistivity imager方位电阻率成像测井仪 APD Elevation of Depth Reference (LMF) above Permanent Datum APWD ASI AVG: AVO apparatus whle drilling Array seismic imager 阵列地震成像仪 Average Amplitude Versus Offset(Amplitude variation with offset calibration) 振幅 -炮检距关系 AZI: BBC BGG: Azimuth (deg) Buy Back Contract Background Gas (%) BGP 物探局 BHFP bottomhole flowing pressure BHS :Borehole Status BHT :Bottom Hole Temperature BHTA BHTT 声波幅度 声波返回时间 BLWH Blue White BML below mud line BOP Blow out preventer BOP stack 防喷器组 BS Bit Size BSW basic?? saturation water(综合含水) CAL borehole diameter 井径 CAST 声波扫描成像测井仪 CBI Central Bank of Iran CBIL 井周声波成像 CBL CC CCAL CCL CCM CDF CDF Cement Bond Log correlation coefficient common core analysis 常规岩心分析 Casing Collar Locator Contractors Committee Meeting cumulative density function Calibrated Downhole Force
阅读下面的材料，根据要求作文。 1 21世纪，会带给我们些什么呢？面对新世纪的曙光，我们对新世纪有太多太多的渴望和憧憬，但也清楚地知道，不尽的未来带给我们的还有太多太多的未知以及什么都可能有的变数。 请以"新世纪，我的渴望和憧憬"为话题写一篇文章。 【要求】①立意自定；②文体不限；③题目自拟；④不少于800字。 【提示】本题属对象和时间的限制。写作时要注意"我"和"新世纪"，要写出自己的真情实感，要具有鲜明的时代感。 2 阅读下面一首短诗，根据要求作文。 散步的时候/ 我走直路/ 儿子却故意/ 把路走弯/ 我说/ 把路走直/ 就是捷径/ 儿子说/ 把路走弯/ 路就延长 请以"选择"为话题，写一篇抒发你对自己人生路的感受，或阐发你对人生路的看法的文章。【要求】①立意自定；②文体不限；③题目自拟；④不少于800字。 【提示】本题属范围的限制。作文选材范围是多方面的，如学生生活、社会生活、人生感悟、传统美德、哲理思辩等。本文内容一定是对"人生路"的感受或看法。 3 阅读下面的材料，根据要求作文。 人生有"四气"：奋发向上、百折不回的志气；铁面无私、令人敬畏的正气；披荆斩棘、舍生取义的勇气；求新求好、能做善做的才气。 请根据材料，以"人生的关键"为话题写一篇文章。 【要求】①立意自定；②文体不限；③题目自拟；④不少于800字。 【提示】本题属主旨的限制。文章主旨即为"四气"中的某一"气"，如：人生的关键是要有奋发向上、百折不回的志气。 4 阅读下面一则寓言，根据要求作文。 海滩上撒满了彩色的贝壳，一群孩子在拾着。一个孩子捡起一枚贝壳，随手又把它丢弃。他已经寻找了一个下午，始终没有找到自己心目中那枚最美、最稀罕的贝壳。夕阳西下，海与天连成一片深深的蓝色，他的伙伴们已经捡了满满一篮子贝壳，只有他仍然拖着沉重的脚步在海滩上寻找…… 请以寓言的寓意为话题写一篇文章。 【要求】①不得只改写、扩写材料；②文体不限；③题目自拟；④不少于800字。 【提示】本题属主旨的限制。这则寓言实际上讲的是人们对人生目标的两种态度：或执着追求崇高的理想，或脚踏实地从小事做起。 5 阅读下面的材料，根据要求作文。 宋朝大文豪苏轼读到王安石的《咏菊》"昨夜西风过园林，吹落黄花满地金"后，认为菊花并不落瓣，于是随后写道："秋花不比春花落，说与诗人仔细吟。"后来苏轼调任黄州团练副使，在重阳节后的一天步入菊园，只见满地铺金，枝上已无一朵菊花，到此才知，同为菊花竟也有落瓣与不落瓣之分。
谷歌浏览器设置及常用快捷键 导入书签：可从右上角“其他书签”中导入IE或者其他浏览器的书签； 选择主页：点击扳手图标，然后选择“选项”，设置主页。 停靠书签栏：将书签栏放在地址栏的下方，方便您访问书签和书签文件夹，要停靠书签栏，请依次选择扳手菜单> 工具> 总是显示书签栏。也可以用快捷键（Ctrl+Shift+B）打开或关闭书签栏。 主题挑选：点击扳手菜单→选项→个人资料。 将谷歌浏览器设置为默认浏览器：点击扳手菜单→选项→基本设置，点击默认浏览器按钮。常用快捷键： Ctrl+T：打开新标签页，或者直接点击当前标签页右边“+”号。 Ctrl+O：在谷歌浏览器中打开文件。 Ctrl+Shift+B ：打开或关闭书签栏。 Ctrl+F：打开查找栏。 Shift+Esc：打开谷歌浏览器任务管理器。 Ctrl+N：打开新窗口。 按住Ctrl键的同时点击链接，从新标签页中打开链接。 按住Shift键的同时点击链接，从新窗口中打开链接。 Ctrl+Shift+T重新打开上次关闭的标签页，谷歌浏览器可记住最近关闭的10个标签页。 Ctrl+1到Ctrl+8切换到标签栏中指定位置编号所对应的标签页。 Ctrl+9切换到最后一个标签页。 Ctrl+Tab或Ctrl+PgDown切换到下一个标签页。 Ctrl+Shift+Tab或Ctrl+PgUp切换到上一个标签页。 Alt+F4：关闭当前窗口。 Ctrl+W或Ctrl+F4关闭当前标签页或弹出窗口。 Alt+Home：在当前窗口打开主页。 Ctrl+H：打开“历史记录”页面。 Ctrl+J：打开“下载内容”页面。 Shift+Alt+T：选中浏览器工具栏中的第一个工具，按Tab、Shift+Tab、Home、End、向右箭头和向左箭头，可在工具栏中选择各个工具选项，再按空格键或Enter 可激活工具栏按钮。按Esc 可将焦点从工具栏移回到网页上。 Ctrl+Shift+Delete：打开“清除浏览数据”对话框。 F6 或Ctrl+L或Alt+D选中当前网页网址。 Ctrl+P：打印当前网页。 Ctrl+S ：保存当前网页。 F5 或Ctrl+R 重新载入当前网页。 Esc停止载入当前网页。 Ctrl+F 打开查找栏。 Ctrl+G 或F3 在查找栏中查找下一条与输入内容相匹配的内容。 Ctrl+F5 或Shift+F5 重新载入当前网页，忽略缓存的内容。 按住Alt 键，然后点击链接，下载链接目标。 Ctrl+U 打开当前网页的源代码。
膅EVT(Engineering Verification Test)工程验证测试阶段 膁DVT(Design Verification Test)设计验证测试阶段 艿DMT（Design Maturity Test）成熟度验证 腿MVT（Mass-Production Verification Test）量产验证测试 薃PVT(Production/Process Verification Test)生产/制程验证测试阶段膄MP(Mass Production)量产 莈工程师类: 芆PE: Product Engineer 产品工程师
莅Process Engineer 制程工程师 羃ME: Mechanical Engineer 机构工程师 莈IE：Industrial Engineer 工业工程师 蚇QE: Quality Engineer 品质工程师 肇SQESupplier Quality Engineer供货商质量工程师 蚂QC quality control 品质管理人员 蒈FQC final quality control 终点质量管理人员 肈IPQC in process quality control 制程中的质量管理人员蒅OQC output quality control 最终出货质量管理人员
蒁IQC incoming quality control 进料质量管理人员薈TQC total quality control 全面质量管理 葿POC passage quality control 段检人员 芇QA quality assurance 质量保证人员 蒄OQA output quality assurance 出货质量保证人员蚈QE quality engineering 品质工程人员 薆TE Test Engineer 测试工程师 蚄AE Automatic Engineer 自动化工程师
键盘快捷键大全 一、常见用法： F1显示当前程序或者windows的帮助内容。 F2当你选中一个文件的话，这意味着“重命名” F3当你在桌面上的时候是打开“查找：所有文件”对话框 F10或ALT激活当前程序的菜单栏 windows键或CTRL+ESC打开开始菜单 CTRL+ALT+DELETE在win9x中打开关闭程序对话框 DELETE删除被选择的选择项目,如果是文件,将被放入回收站 SHIFT+DELETE 删除被选择的选择项目,如果是文件,将被直接删除而不是放入回收站 CTRL+N新建一个新的文件CTRL+O打开“打开文件”对话框 CTRL+P打开“打印”对话框CTRL+S保存当前操作的文件 CTRL+X剪切被选择的项目到剪贴板 CTRL+INSERT 或CTRL+C复制被选择的项目到剪贴板 SHIFT+INSERT 或CTRL+V粘贴剪贴板中的内容到当前位置 ALT+BACKSPACE 或CTRL+Z 撤销上一步的操作 ALT+SHIFT+BACKSPACE重做上一步被撤销的操作
Windows键+M最小化所有被打开的窗口。 Windows键+CTRL+M重新将恢复上一项操作前窗口的大小和位置 Windows键+E打开资源管理器 Windows键+F打开“查找：所有文件”对话框 Windows键+R打开“运行”对话框 Windows键+BREAK打开“系统属性”对话框 Windows键+CTRL+F打开“查找：计算机”对话框 SHIFT+F10或鼠标右击打开当前活动项目的快捷菜单 SHIFT在放入CD的时候按下不放，可以跳过自动播放CD。在打开word的时候按下不 放,可以跳过自启动的宏 ALT+F4关闭当前应用程序ALT+SPACEBAR打开程序最左上角的菜单 ALT+TAB切换当前程序ALT+ESC切换当前程序 ALT+ENTER将windows下运行的MSDOS窗口在窗口和全屏幕状态间切换 PRINT SCREEN将当前屏幕以图象方式拷贝到剪贴板 ALT+PRINT SCREEN将当前活动程序窗口以图象方式拷贝到剪贴板 CTRL+F4关闭当前应用程序中的当前文本（如word中）