-- *****************************************************************
-- PT-SMI:	Promise Technology Product Structure of Management Information
--
-- April 2003, Keh-hoh Lii
--
-- Copyright (c) 2003 Promise Technology, Inc.
-- All rights reserved.
-- 
-- *****************************************************************

PT-SMI DEFINITIONS ::= BEGIN

IMPORTS
	MODULE-IDENTITY,
	OBJECT-IDENTITY,
	enterprises
		FROM SNMPv2-SMI;

promise MODULE-IDENTITY
	LAST-UPDATED	"200304170000Z" 
	ORGANIZATION	"Promise Technology, Inc."
	CONTACT-INFO
		"	Promise Technology, Inc.

		Postal: 1745 McCandless Drive	
			Milpitas, CA 95035
			USA

		 Phone:	+1 408 228 6300
		   Fax: +1 408 228 6401

		E-mail:	sales@promise.com"
	DESCRIPTION
		"The Structure of Management Information for the Promise Technolofy enterprise."
	REVISION	"200304170000Z" 
	DESCRIPTION
		"Created"
	::= { enterprises 7933 }                               
 
--
-- Promise Technology top level sub-trees
--
ptProducts OBJECT-IDENTITY
	STATUS	current
	DESCRIPTION
		"ptProducts is the root object identifier from
		 which sysObjectID values are assigned."
	::= { promise 1 }
 
ptGeneric OBJECT-IDENTITY
	STATUS	current
	DESCRIPTION
		"ptGeneric provides a root object identifier
		 from which all generic MIBs among products may be assigned."
	::= { promise 2 }

ptRegistration OBJECT-IDENTITY
	STATUS	current
	DESCRIPTION
		"ptRegistration provides a root object identifier
		 from which MODULE-IDENTITY values may be assigned.
		 It is also used to register individual product."
	::= { promise 3 }

otherEnterprises OBJECT-IDENTITY
	STATUS	current
	DESCRIPTION
		"otherEnterprises provides a root object identifier
		from which mibs produced by other companies may be
		placed."
	::= { promise 4 }
  
ptAgentCapability OBJECT-IDENTITY
	STATUS	current
	DESCRIPTION
		"ptAgentCapability provides a root object identifier
		from which AGENT-CAPABILITIES values may be assigned."
	::= { promise 5 }

ptExperiment OBJECT-IDENTITY
	STATUS	current
	DESCRIPTION
		"ptExperiment provides a root object identifier
		from which experimental mibs may be temporarily
		based."
	::= { promise 6 }

 	
--
--  In order to have unique OID and consistent MIBs definition across the company
--  used by individual MIB developers, all top level of generic, products and there 
--  corresponding modules OID should be registered here. 
--  Ask your MIB administrator to create a new top level MIB and module
--  OIDs for the product you are working on in this file and imports 
--  them in your MIB module.  
-- 
ptGenericModules        OBJECT IDENTIFIER ::= { ptRegistration 1 }
ptProductModules        OBJECT IDENTIFIER ::= { ptRegistration 2 }
  
--  Every single product should have an unique OID to identify it.  This OID is to be
--  assigned to sysObjectID so management system can read it.  'ptProductRegistration'
--  is the top level node used for this purpose.

ptProductRegistration   OBJECT IDENTIFIER ::= { ptRegistration 3 }

-- Generic MIBs registration.  
-- These are the MIBs that shared by multiple products. 
-- Each generic MIB should have only a single MIB MODULE associate with it.
-- Use ptGenDskAry as an example, its MIB modules looks like the following:
--
-- 		IMPORTS ptGenDskAry, ptGenericModules
-- 			FROM PT-SMI
--		ptSonomaModule MODULE-IDENTITY
--					.
--					.
--		::= { ptGenericModules 1}
--
-- You can then define any sub-trees under ptGenDskAry as you wish.
 
ptGenDskAry		OBJECT IDENTIFIER ::= { ptGeneric 1 }
ptGenEvents		OBJECT IDENTIFIER ::= { ptGeneric 2 }
ptGenIscsi		OBJECT IDENTIFIER ::= { ptGeneric 3 }

-- Product MIBs registration. 
--
-- Using FastTrak as an example: 
--
-- Each product family is assigned a unique top level node OID (ptRastTrak) 
-- and a MODULE OID (ptFastTrakModules).
-- FastTrak MIB modules looks like the following:
--
-- 		IMPORTS ptFastTrak, ptFastTrakModules
-- 			FROM PT-SMI
--		ptFastTrakModule MODULE-IDENTITY
--					.
--					.
--		::= { ptFastTrakModules n}     
--
--		fasttrakCard OBJECT IDENTIFIER ::= { ptFastTrak 1 }
--
-- Where n is an unique number greater than or equal to 1 that assigned by FaskTrak MIB  
-- designer for each FastTrak MIB module. 
--
-- Although all FaskTrak family members (FT-TX2, FT-TX4, FT-TX378 and FT-TX400) share the same MIBs,
-- they are different product, so each of them should have an unique OID assigned to it. For example,
-- since 'ptFastTrakTx2Reg' is assigned to FT-TX2 as below, FT-TX2 SNMP agent should set 'sysObjectID' 
-- defined in MIB-II to OID 'ptFastTrakTx2Reg'.
 
ptFastTrak 				OBJECT IDENTIFIER ::= { ptProducts 2 }	
ptFastTrakModules   	OBJECT IDENTIFIER ::= { ptProductModules 2 }
ptFastTrakReg   		OBJECT IDENTIFIER ::= { ptProductRegistration 2 }
 ptFastTrakTx2Reg   	OBJECT IDENTIFIER ::= { ptFastTrakReg 1 }
 ptFastTrakTx4Reg   	OBJECT IDENTIFIER ::= { ptFastTrakReg 2 }
 ptFastTrakTx378Reg   	OBJECT IDENTIFIER ::= { ptFastTrakReg 3 }
 ptFastTrakTx2400Reg   	OBJECT IDENTIFIER ::= { ptFastTrakReg 4 }

ptSonoma 				OBJECT IDENTIFIER ::= { ptProducts 5 }	
ptSonomaModules   		OBJECT IDENTIFIER ::= { ptProductModules 5 }
ptSonomaReg   			OBJECT IDENTIFIER ::= { ptProductRegistration 5 }

ptIrvine 				OBJECT IDENTIFIER ::= { ptProducts 6 }	
ptIrvineModules  		OBJECT IDENTIFIER ::= { ptProductModules 6 }
ptIrvineReg 			OBJECT IDENTIFIER ::= { ptProductRegistration 6 }	

ptIslaVista 			OBJECT IDENTIFIER ::= { ptProducts 7 }	
ptIslaVistaModules   	OBJECT IDENTIFIER ::= { ptProductModules 7 }
ptIslaVistaReg 			OBJECT IDENTIFIER ::= { ptProductRegistration 7 }	

ptCarmel 				OBJECT IDENTIFIER ::= { ptProducts 8 }	
ptCarmelModules   		OBJECT IDENTIFIER ::= { ptProductModules 8 }
ptCarmelReg 			OBJECT IDENTIFIER ::= { ptProductRegistration 8 }	

ptSalinas 				OBJECT IDENTIFIER ::= { ptProducts 9 }	
ptSalinasModules   		OBJECT IDENTIFIER ::= { ptProductModules 9 }
ptSalinasReg 			OBJECT IDENTIFIER ::= { ptProductRegistration 9 }	

END