Paradyne 3150 Operator's Manual

Also see for 3151: Quick installation Release note Information guide Quick reference Quick reference

Contents

Paradyne 3150 Operator's Manual Manual pdf 118 page image

SNMP MIB ObjectsE-73150-A2-GB21-80 February 1998IP Group – “ipRouteMetric2” Object(ipRouteEntry 4)The following values are displayed for theipRouteMetric2 object. For a carrier device designated asthe IP Bus Master, ipRouteMetric2 is used to designatethe slot number of the next hop associated with this routeif the destination is not connected to the device. Forcarrier devices not designated as the IP Bus Master or IPBus Master devices in which the destination is connectedto the device, ipRouteMetric2 contains the slot number(0–15) of the carrier device. For standalone devices,ipRouteMetric2 is not used and contains –1.When adding a route to the routing table using SNMP,do not specify a value for ipRouteMetric2.IP Group – “ipRouteProto” Object(ipRouteEntry 9)This object is a read-only object and may have thefollowing values in the CSU.• other(1) – Temporary route added by IP.• local(2) – Route added or modified as a result ofuser configuration via the front panel.• netmgmt(3) – Route added or modified by means ofan SNMP set.• icmp(4) – Route added or modified by InternetControl Management Protocol (ICMP).• rip(8) – Route added or modified by RoutingInformation Protocol (RIP) (or similar proprietaryprotocol).IP Group – “ipRouteAge” Object(ipRouteEntry 10)This object is implemented as a read-only object in theCSU. In the CSU, it reflects the value of the route’stime-to-live (in seconds). When displays, a value of 999represents a route that is retained permanently. Fortemporary routes, the ipRouteAge object decrements overtime. All routes added via an SNMP set of theipRouteTable are considered permanent routes. Theseroutes do not age, but will remain unless deleted viaSNMP.ICMP Group, MIB IIThe ICMP Group objects are fully supported by theCSU.TCP Group, MIB IIThe TCP Group objects are fully supported by theDSU/CSU, with the exception of the tcpConnState object,which will be read-only.UDP Group, MIB IIThe User Datagram Protocol (UDP) Group objects arefully supported by the CSU.Transmission Group, MIB IIObjects in the transmission group are supported on thenetwork and DTE interfaces, the COM port, the MODEMport, and the AUX port. The objects in the transmissiongroup are not defined within MIB II, but rather throughother Internet standard MIB definitions. The followingtwo transmission group objects are supported by the CSU.• ds1 (transmission 18) – The transmission objectsupported on the T1 interfaces.• rs232 (transmission 33) – The transmission objectsupported on the COM port, AUX port, andMODEM port.The “ds1” transmission object is defined by theDS1/E1 MIB. The rs232 transmission object is defined bythe RS-232-like MIB.SNMP Group, MIB IIThe SNMP Group objects that apply to a managementagent are fully supported by the CSU. The followingobjects apply only to an NMS and return a zero value ifaccessed.• snmpInTooBigs (snmp 8)• snmpInNoSuchNames (snmp 9)• snmpInBadValues (snmp 10)• snmpInReadOnlys (snmp 11)• snmpInGenErrs (snmp 12)• snmpInGetResponses (snmp 18)• snmpInTraps (snmp19)• snmpOutGetRequests (snmp 25)• snmpOutGetNexts (snmp 26)• snmpOutSetRequests (snmp 27)