LSI-ROUTER-API-INTERFACE-MIB DEFINITIONS ::= BEGIN IMPORTS PortNumber, Unsigned16, lsiGenericModules FROM LSIROOT-MIB OBJECT-GROUP FROM SNMPv2-CONF MODULE-IDENTITY, OBJECT-IDENTITY, OBJECT-TYPE FROM SNMPv2-SMI DisplayString FROM SNMPv2-TC ; routerAPIinterfaceMIB MODULE-IDENTITY LAST-UPDATED "201007302003Z" -- July 30, 2010 ORGANIZATION "Logical Solutions, Inc." CONTACT-INFO "support@thinklogical.com" DESCRIPTION "Generic SNMP objects for the Router ASCII API." REVISION "201007301251Z" -- July 30, 2010 DESCRIPTION "Reviewing, adding and modifying Description fields" REVISION "201006011424Z" -- June 01, 2010 DESCRIPTION "added a filed to return the VxRouter alarm bits (xalarm command)." REVISION "200910292113Z" -- October 29, 2009 DESCRIPTION "Added notifications for cards and connections" ::= { lsiGenericModules 1 } routerAPIInterfaceObjects OBJECT IDENTIFIER ::= { routerAPIinterfaceMIB 1 } routerAPIinterfaceData OBJECT-IDENTITY STATUS current DESCRIPTION "This node contains all the data objects defined in this MIB." ::= { routerAPIInterfaceObjects 1 } routerAPIChassisType OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current DESCRIPTION "Type of chassis. Currently we have 3 types: Vx40Router, Vx160Router, Vx320Router" ::= { routerAPIinterfaceData 1 } routerAPINumberOfBackplanes OBJECT-TYPE SYNTAX Unsigned16 MAX-ACCESS read-only STATUS current DESCRIPTION "Returns the number of backplanes in the switching system. These may be physical backplanes or logical backplanes. (the Vx40 router consists of 1 physical backplane that is treated by the software as 2 logical backplanes). Each backplane can switch data in one direction only: from a LSI transmitter to a LSI receiver, or from receiver to transmitter. Additionally, a backplane may allow 1 input to be sent to only 1 output (P2P or point-to-point mode), or to multiple outputs at the same time." ::= { routerAPIinterfaceData 2 } routerAPINumSwitchesPerBackplane OBJECT-TYPE SYNTAX Unsigned16 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of (logical) crosspoint switches in the system. The VX160Router has 2, 1 per backplane. The Vx320 has 8 (4 per backplane), but logically they function as 2." DEFVAL { 2 } ::= { routerAPIinterfaceData 3 } routerAPINumSensorsPerBackplane OBJECT-TYPE SYNTAX Unsigned16 MAX-ACCESS read-only STATUS current DESCRIPTION "How many Temperature sensors on each backplane: Vx40 - 3 Vx160 - 4 Vx320 - 4" ::= { routerAPIinterfaceData 4 } routerAPINumberOfCards OBJECT-TYPE SYNTAX Unsigned16 MAX-ACCESS read-only STATUS current DESCRIPTION "Maximum number of cards (input and output) in the system. Half the cards are input/upstream, half are output/downstream." ::= { routerAPIinterfaceData 5 } routerAPINumberOfPorts OBJECT-TYPE SYNTAX PortNumber MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of inputs OR outputs the system can support." ::= { routerAPIinterfaceData 6 } routerAPINumPortsPerCard OBJECT-TYPE SYNTAX Unsigned16 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of I/O ports (SFPs) per I/O card. The VX160 has 20 ports per card." DEFVAL { 20 } ::= { routerAPIinterfaceData 7 } routerAPINumberOfPowerSupplys OBJECT-TYPE SYNTAX Unsigned16 (0..8) MAX-ACCESS read-only STATUS current DESCRIPTION "The number of power supplies in the system." DEFVAL { 2 } ::= { routerAPIinterfaceData 8 } routerAPINumberOfFanTrays OBJECT-TYPE SYNTAX Unsigned16 (0..8) MAX-ACCESS read-only STATUS current DESCRIPTION "The number of fan trays in the system." DEFVAL { 1 } ::= { routerAPIinterfaceData 9 } routerAPINumFansPerTray OBJECT-TYPE SYNTAX Unsigned16 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of fans in a tray." DEFVAL { 3 } ::= { routerAPIinterfaceData 10 } routerAPIChassisInfo OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current DESCRIPTION "This returns a string that consists of 3 numbers separated by commas. The first number is the number of video ports in the chassis. The second number is the number of data/KMASS ports. The third number is the numeric offset to be used in a chassis that has both video and data ports (StudioPro). A Video dcs will set the 2nd number to 0; a KMASS dcs will set the 1st number to 0. In both cases the 3rd number will be 0. This data will allow an external program to determine the number of each type of ports in a chassis. The routerAPIinterfaceNumberOfPorts OID only returns the total number of ports in a chassis. Curently the third number (offset) is not used by the SNMP Agent. Thus, in the StudioPro example below, the first data port must be accessed as port 17 and the last port as port 48. They can NOT be accessed via SNMP as ports 801 through 832. When the Agent accepts the offset value, it will return a non-zero value. Video 72: 72,0,0 KMASS 144: 0,144,0 StudioPro: 16,32,0 VX160Router: 0,160,0" ::= { routerAPIinterfaceData 11 } routerAPIalarms OBJECT-TYPE SYNTAX Unsigned16 MAX-ACCESS read-only STATUS current DESCRIPTION "The value returned depends on 2 items: 1) VxRouter Model and 2) which alarms are active. If there are no alarms (or the device does not support alarms) the value returned is zero. The 40-port & 160-port VxRouters have the same 8 alarms. The 320-port VxRouter has two additional power supply alarms. It it left up to the user to determine which model VxRouter is in use. Each alarm is associated with a bit, a zero meaning the alarm is off. In the list below, bit 0 is the LSB and bit 7 (or 9) is the MSB. Bit Vx40 & Vx160 Vx320 0 PS1 PS1 1 PS2 PS2 2 Fan PS3 3 High Temperature Warning PS4 4 High Temperature Shutdown Fan 5 CPU High Temperature Warning 6 I/O card High Temperature Shutdown 7 Any CPU 8 I/O card 9 Any The 'Any' alarm is set if any of the other alarms are active. An unsigned integer value is returned. The use must decode the bits to determine which alarms, if any, are active. Examples: (Vx40 or Vx160) 130 decimal equals 82h, Bits 7 and 2 Fan and Any alarms (Vx320) 529 decimal equals 211h, Bits 9, 4, and 1 PS1, Fan and Any alarms" ::= { routerAPIinterfaceData 12 } routerAPIinterfaceConformance OBJECT IDENTIFIER ::= { routerAPIinterfaceMIB 2 } routerAPIinterfaceGroups OBJECT IDENTIFIER ::= { routerAPIinterfaceConformance 1 } routerAPIObjectGroup OBJECT-GROUP OBJECTS { routerAPIalarms, routerAPIChassisInfo, routerAPIChassisType, routerAPINumberOfBackplanes, routerAPINumberOfCards, routerAPINumberOfFanTrays, routerAPINumberOfPorts, routerAPINumberOfPowerSupplys, routerAPINumFansPerTray, routerAPINumPortsPerCard, routerAPINumSensorsPerBackplane, routerAPINumSwitchesPerBackplane } STATUS current DESCRIPTION "Required group, contains all the objects in this MIB" ::= { routerAPIinterfaceGroups 2 } END