---
oid: "1.3.6.1.4.1.119.2.3.14.9.4.6.1.1"
asn1-notation: "{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 119 nec-mib(2) necProductDepend(3) atomis-mib(14) m7-phase2-mib(9) conn(4) connSoftPvcEstablishedSrcInfTable(6) connSoftPvcEstablishedSrcInfEntry(1) connSoftPvcEstablishedSrcInf(1)}"
description: "connSoftPvcEstablishedSrcInf OBJECT-TYPE"
classification: "MIB object for network management"
last-modified: "2020-11-13"
---

## OID : `1.3.6.1.4.1.119.2.3.14.9.4.6.1.1`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 119 nec-mib(2) necProductDepend(3) atomis-mib(14) m7-phase2-mib(9) conn(4) connSoftPvcEstablishedSrcInfTable(6) connSoftPvcEstablishedSrcInfEntry(1) connSoftPvcEstablishedSrcInf(1)}
```

### Description

```asn1
connSoftPvcEstablishedSrcInf OBJECT-TYPE
SYNTAX Opaque
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The calling node information of the Soft PVPC/PVCC
established as called side office by the node.
The structure of the entry is as follows
struct {
long SrcAtmAddressFormat;
long SrcAtmAddressLength;
char SrcAtmAddress\[20\];
};
(\*1) 'long' data should be stored with 'big endian'.
(\*2) For SrcAtmAddress data, if it is less than 20 byte,
the data padded by '0xf' shall be stored.
This information is divided into up to 32 pieces, and each
piece is put into the head 4 bytes (count) of an entry. The
data which contains the number of the entries is described
below.
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--+
\| count \| (= n)
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--+
\| EstSrcInf 1 \|
\|\...\...\...\...\.....\|
\| EstSrcInf 2 \|
\|\...\...\...\...\.....\|
\| . \|
\| . \|
\| . \|
\|\...\...\...\...\.....\|
\| EstSrcInf n \| ( 1 \<= n \<= 32 )
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--+"
```

**Classification**: MIB object for network management

### Child OIDs

No child OID

### Terms of Use
[Terms of use](https://oid-base.com/disclaimer.htm.md)
