Reference record for OID 1.3.6.1.6.3.17.1.4

parent

1.3.6.1.6.3.17.1 (marsClientObjects)

node code

4

node name

marsClientVcTable

dot oid

1.3.6.1.6.3.17.1.4

type

OBJECT-TYPE

asn1 oid

{iso(1) identified-organization(3) dod(6) internet(1) snmpV2(6) snmpModules(3) marsMIB(17) marsClientObjects(1) marsClientVcTable(4)}

{iso(1) org(3) dod(6) internet(1) snmpV2(6) snmpModules(3) marsMIB(17) marsClientObjects(1) marsClientVcTable(4)}

{iso(1) iso-identified-organization(3) dod(6) internet(1) snmpV2(6) snmpModules(3) marsMIB(17) marsClientObjects(1) marsClientVcTable(4)}

iri oid

/iso/identified-organization/dod/internet/snmpV2/snmpModules/marsMIB/marsClientObjects/marsClientVcTable

/iso/org/dod/internet/snmpV2/snmpModules/marsMIB/marsClientObjects/marsClientVcTable

/iso/iso-identified-organization/dod/internet/snmpV2/snmpModules/marsMIB/marsClientObjects/marsClientVcTable

iri by oid_info

/ISO/Identified-Organization/6/1/6/3/17/1/4

Description by mibdepot

This table contains information about open virtual
circuits (VCs) that a client has. For point to point
circuit, each entry represents a single VC connection
between this client ATM address to another party ATM
address. In the case of point to multipoint connection
where a single source address is associated with
multiple destinations, several entries are used to
represent the relationship. An example of point to
multi-point VC represented in a table is shown below.

Client VPI/VCI Grp Addr1/Addr2 Part Addr
1 0,1 g1,g2 p1
1 0,1 g1,g2 p2
1 0,1 g1,g2 p3

Note: This table assumes the IP multicast address
groups (min, max) defined in each entry are
always consecutive. In the case of that a
client receives a JOIN/LEAVE with
mars$flag.punched set, each pair of the IP
groups will first be broken into several
pairs of consecutive IP groups before each
entry row corresponding to a pair of IP group
is created.

Parsed from file rfc2417-Multicast-over-UNI-3.0-A63.1-based-ATM-Networks-IPATM-IPMC.mib.txt
Company: ietf_rfcs
Module: IPATM-IPMC-MIB

Information by oid_info

Vendor: IETF RFCs
Module: IPATM-IPMC-MIB (rfc2366-Multicast-over-UNI-3.0-A63.1-based-ATM-Networks-IPATM-IPMC.mib)
Type: TABLE
Access: not-accessible
Syntax: SEQUENCE OF

Automatically extracted from www.mibdepot.com

Information by mibdepot

marsClientVcTable OBJECT-TYPE
       SYNTAX  SEQUENCE OF MarsClientVcEntry
       MAX-ACCESS  not-accessible
       STATUS current
       DESCRIPTION
           "This table contains information about open virtual
            circuits (VCs) that a client has.  For point to point
            circuit, each entry represents a single VC connection
            between this client ATM address to another party ATM
            address.  In the case of point to multipoint connection
            where a single source address is associated with
            multiple destinations, several entries are used to
            represent the relationship.  An example of point to
            multi-point VC represented in a table is shown below.

                   Client    VPI/VCI    Grp Addr1/Addr2    Part Addr
                     1         0,1          g1,g2             p1
                     1         0,1          g1,g2             p2
                     1         0,1          g1,g2             p3

            Note:  This table assumes the IP multicast address
                   groups (min, max) defined in each entry are
                   always consecutive.  In the case of that a
                   client receives a JOIN/LEAVE with
                   mars$flag.punched set, each pair of the IP
                   groups will first be broken into several
                   pairs of consecutive IP groups before each
                   entry row corresponding to a pair of IP group
                   is created."
       ::= { marsClientObjects 4 }

First Registration Authority (recovered by parent 1.3.6)

Defense Communication Agency

Current Registration Authority (recovered by parent 1.3.6)

US DoD

Children (1)

Brothers (4)