Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"relayAgentConfiguration",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"notUsed",
"(",
"0",
")",
",",
"remoteIdString",
"(",
"1",
")",
",",
"remoteIdCisco",
"(",
"2",
")",
",",
"remoteIdCustomer",
"(",
"3",
")",
",",
"circuitIdString",
"(",
"4",
")",
",",
"circuitIdCustomer",
"(",
"5",
")",
",",
"remoteIdEda",
"(",
"6",
")",
",",
"circuitIdEda",
"(",
"7",
")",
",",
"circuitIdTR101",
"(",
"8",
")",
"}",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"Determines which Relay Agent configuration to use (DHCP or PPPoE). DHCP: The relay agent adds DHCP option 82 to upstream DHCP requests, and removes the option 82 from downstream DHCP replies. See also RFC 3046. PPPoE: The relay agent adds a vendor specific option (AtmForum=353) to upstream PADR frames. The information is encoded similar to the suboptions in DHCP option 82. No standard currently exists (Juniper/BRAS interworking). 0 - notused: No relay-agent information will be added or removed from the frames. 1 - remoteIdString: A specified string will be inserted as 'Agent Remote ID' (sub-option 2). The parameter relayAgentString has to be set with the string before using this configuration. 2 - remoteIdCisco: The 'Agent Remote ID' (sub-option 2), is encoded as 'Routed Bridge Encapsulation' specified by Cisco. 3 - remoteIdCustomer: The customer Id will be inserted as a string in sub-option 2, Agent Remote ID, in the option 82 field. The parameter relayAgentString has to be set with the correct customer Id before using this configuration. 4 - circuitIdString: Same as remoteIdString except that it will be encoded in 'Agent Circuit ID' (sub-option 1). Example: '172.30.38.83 atm 0/1:100.33' (relay-agent=172.30.38.83,slot=0,port=1,vpi=100,vci=33) 5 - circuitIdCustomer: Same as remoteIdCustomer except that it will be encoded in 'Agent Circuit ID' (sub-option 1). 6 - remoteIdEda: EDA specified coding of the relay agent information (sub-option 2). The parameters relayAgentEdaIp and relayAgentEdaNodeId have to be set before using this option when the IP-DSLAM is running in managed mode. 7 - circuitIdEda: EDA specified coding of the relay agent information (sub-option 1). The parameters relayAgentEdaIp and relayAgentEdaNodeId have to be set before using this option when the IP-DSLAM is running in managed mode. 8 - circuitIdTR101: The standard TR-101 Access Loop Identification Syntax will be inserted as 'Agent Circuit ID' (sub-option 1). Example : 'Access-Node-Identifier atm slot/port:vpi.vci'. Access-Node-Identifier: Is the IP address of the management interface. For a stand-alone IP-DSLAM, the IP-DSLAM's own IP address is used, for MSAN and EAN the IP address specified with MIB parameter relayAgentEdaIp is used. atm/eth : Layer-2 type currently used on the user interface. slot : For the stand-alone IP-DSLAM slot value is 0 (zero), for EAN and MSAN this value contains the first 3 bytes of parameter relayAgentEdaNodeId. port : LineId + the last byte of relayAgentEdaNodeId. \"",
"::=",
"{",
"pvcEntry",
"19",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"notUsed",
0
],
[
"remoteIdString",
1
],
[
"remoteIdCisco",
2
],
[
"remoteIdCustomer",
3
],
[
"circuitIdString",
4
],
[
"circuitIdCustomer",
5
],
[
"remoteIdEda",
6
],
[
"circuitIdEda",
7
],
[
"circuitIdTR101",
8
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Determines which Relay Agent configuration to use (DHCP or PPPoE). DHCP: The relay agent adds DHCP option 82 to upstream DHCP requests, and removes the option 82 from downstream DHCP replies. See also RFC 3046. PPPoE: The relay agent adds a vendor specific option (AtmForum=353) to upstream PADR frames. The information is encoded similar to the suboptions in DHCP option 82. No standard currently exists (Juniper/BRAS interworking). 0 - notused: No relay-agent information will be added or removed from the frames. 1 - remoteIdString: A specified string will be inserted as 'Agent Remote ID' (sub-option 2). The parameter relayAgentString has to be set with the string before using this configuration. 2 - remoteIdCisco: The 'Agent Remote ID' (sub-option 2), is encoded as 'Routed Bridge Encapsulation' specified by Cisco. 3 - remoteIdCustomer: The customer Id will be inserted as a string in sub-option 2, Agent Remote ID, in the option 82 field. The parameter relayAgentString has to be set with the correct customer Id before using this configuration. 4 - circuitIdString: Same as remoteIdString except that it will be encoded in 'Agent Circuit ID' (sub-option 1). Example: '172.30.38.83 atm 0/1:100.33' (relay-agent=172.30.38.83,slot=0,port=1,vpi=100,vci=33) 5 - circuitIdCustomer: Same as remoteIdCustomer except that it will be encoded in 'Agent Circuit ID' (sub-option 1). 6 - remoteIdEda: EDA specified coding of the relay agent information (sub-option 2). The parameters relayAgentEdaIp and relayAgentEdaNodeId have to be set before using this option when the IP-DSLAM is running in managed mode. 7 - circuitIdEda: EDA specified coding of the relay agent information (sub-option 1). The parameters relayAgentEdaIp and relayAgentEdaNodeId have to be set before using this option when the IP-DSLAM is running in managed mode. 8 - circuitIdTR101: The standard TR-101 Access Loop Identification Syntax will be inserted as 'Agent Circuit ID' (sub-option 1). Example : 'Access-Node-Identifier atm slot/port:vpi.vci'. Access-Node-Identifier: Is the IP address of the management interface. For a stand-alone IP-DSLAM, the IP-DSLAM's own IP address is used, for MSAN and EAN the IP address specified with MIB parameter relayAgentEdaIp is used. atm/eth : Layer-2 type currently used on the user interface. slot : For the stand-alone IP-DSLAM slot value is 0 (zero), for EAN and MSAN this value contains the first 3 bytes of parameter relayAgentEdaNodeId. port : LineId + the last byte of relayAgentEdaNodeId."
],
null,
null,
null,
null
]
}