marsClientVcTable
IPATM-IPMC-MIB ·
.1.3.6.1.2.1.57.1.4
Object
table
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.
Context
- MIB
- IPATM-IPMC-MIB
- OID
.1.3.6.1.2.1.57.1.4- Type
- table
- Status
- current
- Parent
- marsClientObjects
- Children
- 1
Net-SNMP examples
How SNMP and these commands workUse a bulk walk to inspect objects and instances beneath this OID.
Walk the subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'IPATM-IPMC-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'IPATM-IPMC-MIB::marsClientVcTable'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'IPATM-IPMC-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'IPATM-IPMC-MIB::marsClientVcTable'
Syntax
No syntax metadata recorded.
Values & Constraints
No enumerated values or constraints recorded.