PEA-BRIDGE-IPDSLAM: View SNMP OID List / Download MIB

The IP DSLAM software supports a number of standard and proprietary MIBs. This MIB module defines objects for the management via SNMP of the bridge functionality in the IP DSLAM. The bridge filter functionality from the IP DSLAM is configurable not only per subscriber but also per PVC for a specific subscriber. All the subscribers connected to a specific IP DSLAM share the same physically Ethernet interface, and to protect the subscribers from each other (e.g. from hacking and spoofing) the bridge is implemented with some proprietary filters. One of these filters is a VLAN ID filter. With the use of this filter it is possible to limit the VLAN IDs that a end-user is allowed to use. The filter is implemented as Access Control Lists, so the same filter can be attached to several end-users. For further information about this filter please see the description of the following parameters: - vlanIdAclTable - vlanIdAclRuleTable - pvcUpstreamVlanIdAclId - pvcDownstreamVlanIdAclId This mib contains subscriberInfoTable which contains a list of subscriber information that the IP-DSLAM has dynamically learned. From the table it is possible to read out following information of the subscriber : - MAC address - IP address - virtual MAC address - DHCP lease time - whether subscriber uses fixed forwarding functionality - gateway IP address - gateway MAC address This mib contains the mcastFilterTable which contains multicast filter information for a PVC. Each entry describes a range of consecutive multicast group addresses which are allowed or disallowed. Each multicast group address range is mapped to a multicast Vlan and priority. This mib contains the broadcastStormControl and multicastStormControl which protect the network from upstream broadcast/multicast storms. They will limit the traffic to the thresholds, broadcastStormControlThreshold multicastStormControlThreshold respectively. They can be enabled/disabled with broadcastStormControl multicastStormControl respectively Traffic with all 48 bits in MAC address set to 1 is checked by broadcastStormControl. Traffic that is not broadcast, but with ethernet multicast bit set, is checked by multicastStormControl.

The ADSL subscriber line index.

The PVC index.

A list of entries to the PVCs.

An entry containing PVCs objects for the subscriber line identified by lineIndex.

This is the VLANID to be used for the Ethernet traffic (accordingly to 802.1Q) from and to the specified PVC. It is only used if vlanOperation is set to addonetags or addtwotags. The value can be between 0 and 4095.

The priority (accordingly to 802.1Q) that should be used for the Ethernet frames to and from the specified PVC. It is only used if vlanOperation is set to addonetags or addtwotags. The value can be between 0 and 7 (where 7 is the highest priority).

Show the result of the latest 'ATM OAM F5 end-to-end loopback' test. - notUsed: missing PVC configuration - at least peakCellRate has to be specified - lineDown: line is down - testDisabled: by atmPvcTestOutputTable.atmF5EndToEndLoopbackInterval=0 - testing: until first test in a sequence has finished - failedF5etoe: no reply received on 'OAM F5 end-to-end loopback' cell - createFailed: due to configuration- or resource failure - ok: test succeded for this PVC Please note that even when failed the PVC could still be usable - because the test might not be supported by all CPE's. Enumeration: 'notUsed': 0, 'ok': 5, 'failedF5etoe': 4, 'testing': 3, 'createFailed': 6, 'testDisabled': 2, 'lineDown': 1.

Determines which access method to use for the specific PVC. 0 - DHCP = Use a dynamic IP address (using DHCP). 1 - Static IP = Use a static IP address. 2 - Transparrent LAN = Allow access from all kinds of ethernet packets. All filtering is disabled - VLAN is only security mean. 3 - PPPoE = Use PPPoE as access method. 4 - PPPoA = Use PPPoA as access method. This is converted to PPPoE in the aggregate network. 5 - PPPoX = Autodetect if PPPoE or PPPoA is used on tributary side. 6 - StaticIPoA = Use a static IP address over ATM. This is converted to IP over Ethernet in the aggregate network. 7 - DHCPIPoA = Use a dynamic IP over ATM, which is converted to IP over Ethernet in the aggregate network. 8 - TransparentIPoA = Use a Transparent IP over ATM. This is converted to IP over Ethernet in the aggregate network. Enumeration: 'pppox': 5, 'staticIp': 1, 'pppoe': 3, 'transparrentLan': 2, 'staticIpoa': 6, 'dhcp': 0, 'pppoa': 4, 'transparentIpoa': 8, 'dhcpIpoa': 7.

If True the subscriber is allowed to send and receive all broadcasts on the specified PVC. NOTE: Make special attention toward configuring the correct VLANID for the PVC in order to protect the IP DSLAM, network and subscribers. The value can be either True(1) or False(2).

If True the Ethernet frames originated from the specified PVC will be forwarded to a gateway. The value can be either True(1) or False(2).

The IP Address of the gateway to be used. The value can be any IP address.

If True the DHCP server is used for allocation of IP address. The value can be either True(1) or False(2). If DHCP is not used, an IP address should be added to the filters manually.

The number of Ethernet frames sent downstream. This equals the number of AAL5 frames transmitted. The counter is stored in remotestorage and will survive a restart.

The number of Ethernet frames sent upstream. This equals the number of AAL5 frames received. The counter is stored in remotestorage and will survive a restart.

The downstream traffic payload measured in bytes. This counts the number of bytes transmitted within AAL5 frames, excluding the 6 bytes overhead added by AAL5 itself. The counter is stored in remotestorage and will survive a restart.

The uptream traffic payload measured in bytes. This counts the number of bytes received within AAL5 frames, excluding the 6 bytes overhead added by AAL5 itself. The counter is stored in remotestorage and will survive a restart.

The Virtual Path Identifier for the specified PVC of a subscriber line. The VPI and VCI identifies the PVC (Permanent Virtual Circuit). The value can be between 0 and 15.

The Virtual Chanel Identifier for the specified PVC of a subscriber line. The VCI and VPI identifies the PVC (Permanent Virtual Circuit). The value can be between 0 and 255.

The average downstream PVC rate. The rate has to be lower or equal to the configured ADSL rate and in steps of 32000 bps. Notice: To carry telephony over IP, 192000 bps is needed and the ADSL line must be configured to at least 192000. (the upstream must also be configured to 192000 for full duplex).

The peak downstream PVC rate. The rate has to be lower or equal to the configured ADSL rate and in steps of 32000 bps. Notice: To carry telephony over IP, 192000 bps is needed and the ADSL line must be configured to at least 192000. (the upstream must also be configured to 192000 for full duplex).

If True NO filtering will be performed on the specific PVC. This option gives FULL Layer2 connectivity.

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. Enumeration: 'remoteIdString': 1, 'remoteIdCustomer': 3, 'circuitIdString': 4, 'notUsed': 0, 'circuitIdEda': 7, 'remoteIdEda': 6, 'circuitIdTR101': 8, 'circuitIdCustomer': 5, 'remoteIdCisco': 2.

Specifies the string used in some relayAgentConfiguration's (see 'relayAgentConfiguration' description).

If true upstream ICMP messages are filtered to avoid denial of service attacks. The value can be either True(1) or False(2).

Determines which atm service category to use for the PVC. 0 - UBR = Unspecified bit rate. This is typically used for data applications. 1 - VBR NRT = Variable bit rate - non real-time. (like VBR RT, but not controlling cell delay variance) 2 - VBR RT = Variable bit rate - real-time. This is typically used for multimedia applications. 3 - CBR = Constant bit rate. This is typically used for telephony applications. Enumeration: 'cbr': 3, 'vbrNrt': 1, 'vbrRt': 2, 'ubr': 0.

The maximum number of cells in a burst. Notice: To allow a complete telephony over IP packet to be included in one burst, 4 atm cells are needed. Furthermore, if a VBR service category has been chosen, this parameter cannot be 0.

The peak upstream PVC rate. The rate has to be lower or equal to the configured ADSL rate and in steps of 32000 bps. Notice: To carry telephony over IP, 192000 bps is needed and the ADSL line must be configured to at least 192000. (the downstream must also be configured to 192000 for full duplex).

The average upstream PVC rate. The rate has to be lower or equal to the configured ADSL rate and in steps of 32000 bps. Notice: To carry telephony over IP, 192000 bps is needed and the ADSL line must be configured to at least 192000. (the downstream must also be configured to 192000 for full duplex).

The maximum number of cells in a burst. Notice: To allow a complete telephony over IP packet to be included in one burst, 4 atm cells are needed. Furthermore, if a VBR service category has been chosen, this parameter cannot be 0.

Use 1.3.6.1.4.1.193.72.300.30.1.3.1.38, macAddressCountLimit and 1.3.6.1.4.1.193.72.300.30.1.3.1.37, virtualMacEnable in place of this. Deprecated from: EDA 2.1R1A

If True IGMP Snooping is enabled on the specified PVC. The value can be either True(1) or False(2).

The encapsulation protocol used on top of the AAL5, according to RFC2684. The value is autodetected based on the packets received from the CPE modem. Enumeration: 'llc': 0, 'vcmux': 1.

The actual PPP variant chosen based on the packets received from the CPE modem. The value is only valid if accessMethod is set to pppox (5). Enumeration: 'unknown': 0, 'pppoe': 1, 'pppoa': 2.

Multicast groups which are within the range are allowed. If the multicastGroupsAllowed string is empty, then all multicast groups are allowed. Each range is 8 bytes. To represent the range >=224.10.10.10 <=224.10.10.40, then add: 0xe0 0xa0 0xa0 0xa0 0xe0 0xa0 0xa0 0x28

Counts the number of frames, which have been discarded, due to excessive frame length. The counter can be reset by writing a '0'. (See also: MaximumEthernetFrameSize.)

Upstream Policing can be enabled or disabled on the specific PVC True(1) - ENABLED False(2) - DISABLED.

Counts the number of frames, which have been discarded, due to Upstream Policing. The counter can be reset by writing a '0'.

Multicast groups which are within the range are flooded on all member PVCs and LAN. If the floodMulticastAddrs string is empty, then all multicast packets are handled as video streaming packets. If the floodMulticastAddrs string has the range of >=224.0.0.1 <=224.0.0.40 on PVC1 and PVC9, then all multicast packets received form PVC1 with a dest. address in this range are flooded on PVC9. Each range is 8 bytes. To represent the range >=224.0.0.1 <=224.0.0.40, then add: 0xe0 0x00 0x00 0x01 0xe0 0x00 0x00 0x28 Valid from: EDA 1.3SP1

Using this parameter it is possible to 'trick' the CPE modem to think the BRAS uses a MRU of for instance 1500 bytes (Which it usually can). This can be used to get CPE modems, that discards packets that exceed the standard MRU of 1492, to forward the packets anyway. Setting this value to zero (0) disables the function. This parameter is only valid if access method is set to PPPoA () Valid from: EDA 2.0R2A

Activates the function that exchanges the MAC addresses in the frames that pass, so that only virtual MAC addresses, chosen by the access network are used within the access network. mat-1-1 (1) 1:1 (one-to-one) MAC address translation disabled (2) Original MAC addresses are used within the access network (the use of virtual MAC addresses is disabled) mat-N-1 (3) N:1 (many-to-one) MAC address translation mat-N-1-withLB (4) Like (3) - however extra virtual MAC addresses may be used to provide better load balancing for the Ethernet switches in the aggregation network If virtualMacEnable is not disabled while macAddressCountLimit is 0, then macAddressCountLimit is set to 253 (so that traffic is not stopped inadvertently). Note: Disabling this parameter might jeopardize layer 2 security. Valid from: EDA 3.1 Enumeration: 'disabled': 2, 'mat-N-1': 3, 'mat-1-1': 1, 'mat-N-1-withLB': 4.

A limit for the number of MAC addresses concurrently in use in PVC. Special rules apply when it is set to 0. If virtual MAC functionality is enabled when it is set to 0, then the maximum limit will be 251. If virtual MAC is not enabled when it is set to 0, then no limit is enforced. When virtual MAC addresses are enabled, the virtual Mac address reserved for PPPoA is allowed in addition to the limit set here. Valid from: EDA 2.1R1A

This is the VLAN identifier used only if vlanOperation is configured to addtwotags. This is the inner Vlan used on traffic from and to the specified PVC. The value can be between 0 and 4095. 65535 is a nil-value indicating that inner VLAN is not in use. Valid from: EDA 2.1 SP1

The VLAN priority used only if vlanOperation value is configured to addtwotags. This priority is associated with vlanInnerID accordingly to 802.1Q. The value can be between 0 and 7 (where 7 is the highest priority). 255 is a nil-value indicating that inner VLAN is not in use. Valid from: EDA 2.1 SP1

Indicates the result of testing availability of DHCP Server support within connection. The value is updated only during an IP Connectivity Test, which runs upon initiation via other MIB parameter (ipConnectivityTest). Values: ok (0) The DSLAM has communicated with DHCP server on behalf of the user side and been able to obtain parameters as expected. notOk (1) Communication with DHCP server has been attempted and has failed. notTested (2) Communication with DHCP server has not been attempted, because it was not needed or because test has not been initiated. Valid from: EDA 2.1R1A Enumeration: 'ok': 0, 'notOk': 1, 'notTested': 2.

Indicates the result of testing reachability of default gateway for connection. The value is updated only during an IP Connectivity Test, which runs upon initiation via other MIB parameter (ipConnectivityTest). Values: Ok (0) The DSLAM has sent ICMP Echo Request (Ping) to the Default gateway and received a corresponding Echo Reply. notOk (1) The DSLAM has sent ICMP Echo Request (Ping) to the default gateway but not received a corresponding Echo Reply. notTested (2) The reachability of the default gateway has not been tested because IP Connectivity test has not been initiated. Valid from: EDA 2.1R1A Enumeration: 'ok': 0, 'notOk': 1, 'notTested': 2.

Control and state of IP Connectivity. Values: standBy (0) DSLAM is between tests. This is the default value. This value is written by client when test is finished and when client wishes to stop test prematurely. runTestVMac (1) Written by client when test is to be started and the test may produce frames with Virtual MAC source addresses. done (2) Written by DSLAM when test is completed. busy (3) Written by DSLAM. Whenever the value is ''runTest'' for a connection, the value for any other connection is ''busy''. runTestNoVMac (4) Written by client when test is to be started and the test may not produce frames with Virtual MAC source addresses. N.B. Values (2) done and (3) busy may not be written by client. Normal intended sequence of states: [standby(DSLAM is ready to start test] >>> (client writes) >>> [runTestX(test is being executed)] >>> DSLAM writes >>> [done] >>> (client writes) >>> [standby] In case a test is running when the client writes the value ''runTest'', then the running test is aborted prematurely before the new test is started. This is done regardless of whether the running test is on the same or another connection. Valid from: EDA 2.1R1A Enumeration: 'standBy': 0, 'runTestNoVMac': 4, 'busy': 3, 'done': 2, 'runTestVMac': 1.

DHCP option code to be used when inserting the end-user MAC address to DHCP messages from the end-user. The end-user MAC is inserted in a site-specific DHCP option, thus the valid range is 128 to 254. If set to zero the end-user MAC is not inserted as a site-specific option in DHCP messages. Valid from: EDA 2.0SP3

A parameter which gives the upper limit on the number of Multicast Groups a subscriber can join simultaneously. When exceeded the subscriber will be denied the membership to any new group. If set to zero no limit is enforced. Valid from: EDA 2.1 SP1

Defines the VLAN tag type applied on upstream traffic if. In case of two VLAN tags applied the this VLAN tag type is applied to the outer VLAN tag - qtag: Q/QinQ VLAN tagging. (Ethernet Type 0x8100) - vmantag: VMAN VLAN tagging. (Ethernet Type 0x88A8) - extremevmantag: Extreme VMAN VLAN tagging. (Ethernet Type 0x9100) Valid from: EDA 2.1 SP1 Enumeration: 'extremevmantag': 2, 'vmantag': 1, 'qtag': 0.

Defines the inner VLAN tag type applied on upstream traffic if. - qtag: Q/QinQ VLAN tagging. (Ethernet Type 0x8100) - vmantag: VMAN VLAN tagging. (Ethernet Type 0x88A8) - extremevmantag: Extreme VMAN VLAN tagging. (Ethernet Type 0x9100) Valid from: EDA 2.1 SP1 Enumeration: 'extremevmantag': 2, 'vmantag': 1, 'qtag': 0.

This parameter defines the VLAN operation for the specific PVC. The following values are supported: - addzerotags: The end-users VLAN tags are forwarded transparently without adding any additional tags. Therefore the vlanFilter parameter has to be set to allow tagged traffic (Either Q-tagged or VMAN-tagged). Furthermore a VLAN ID Access Control List is mandatory in order to ensure that the end-user only uses allowed VLAN IDs and to ensure correct switching in the IP-DSLAM. It's possible to associate several VLAN IDs with each end-user when using this operation. This option is valid from EDA 2.2 SP3. - addonetag: The IP-DSLAM will add one VLAN tag. It will be added on top of the end-users tags if any. A maximum of five tags are supported included the one added by the IP-DSLAM. - addtwotags: The IP-DSLAM will add two VLAN tag. They will be added on top of the end-users tags if any. A maximum of five tags are supported included the two added by the IP-DSLAM. Valid from: EDA 2.1 SP1 Enumeration: 'addtwotags': 1, 'addzerotags': 2, 'addonetag': 0.

Defines the types of VLAN tagging a user is allowed to use on upstream traffic. The upstream traffic passes a VLAN filter and if the outermost VLAN tag in the received packet is not allowed the packet is discarded. - untag: Allow untagged traffic. - qtag: Allow Q-tagged traffic. - vmantag: Allow VMAN-tagged traffic. - extremevmantag: Allow Extreme VMAN-tagged traffic. Valid from: EDA 2.1 SP1 Bits: 'extremevmantag': 3, 'vmantag': 2, 'untag': 0, 'qtag': 1.

It is possible to map the priority in a user-provided VLAN to another or the priority in the VLAN(s) applied by the IP DSLAM e.g. if the priority in the user-provided VLAN is 0 the VLAN(s) applied by the IP DSLAM will also be according to this mapping value regardless what is specified in priority/innerVlanPriority. If this value is set to 255 no mapping will take place and the values specified in priority/innerVlanPriority are used. This object entry only handles priority 0. Valid from: EDA 2.1 SP1 Obsoleted from: EDA 2.2 R1A

It is possible to map the priority in a user-provided VLAN to another or the priority in the VLAN(s) applied by the IP DSLAM e.g. if the priority in the user-provided VLAN is 1 the VLAN(s) applied by the IP DSLAM will also be according to this mapping value regardless what is specified in priority/innerVlanPriority. If this value is set to 255 no mapping will take place and the values specified in priority/innerVlanPriority are used. This object entry only handles priority 1. Valid from: EDA 2.1 SP1 Obsoleted from: EDA 2.2 R1A

It is possible to map the priority in a user-provided VLAN to another or the priority in the VLAN(s) applied by the IP DSLAM e.g. if the priority in the user-provided VLAN is 2 the VLAN(s) applied by the IP DSLAM will also be according to this mapping value regardless what is specified in priority/innerVlanPriority. If this value is set to 255 no mapping will take place and the values specified in priority/innerVlanPriority are used. This object entry only handles priority 2. Valid from: EDA 2.1 SP1 Obsoleted from: EDA 2.2 R1A

It is possible to map the priority in a user-provided VLAN to another or the priority in the VLAN(s) applied by the IP DSLAM e.g. if the priority in the user-provided VLAN is 3 the VLAN(s) applied by the IP DSLAM will also be according to this mapping value regardless what is specified in priority/innerVlanPriority. If this value is set to 255 no mapping will take place and the values specified in priority/innerVlanPriority are used. This object entry only handles priority 3. Valid from: EDA 2.1 SP1 Obsoleted from: EDA 2.2 R1A

It is possible to map the priority in a user-provided VLAN to another or the priority in the VLAN(s) applied by the IP DSLAM e.g. if the priority in the user-provided VLAN is 4 the VLAN(s) applied by the IP DSLAM will also be according to this mapping value regardless what is specified in priority/innerVlanPriority. If this value is set to 255 no mapping will take place and the values specified in priority/innerVlanPriority are used. This object entry only handles priority 4. Valid from: EDA 2.1 SP1 Obsoleted from: EDA 2.2 R1A

It is possible to map the priority in a user-provided VLAN to another or the priority in the VLAN(s) applied by the IP DSLAM e.g. if the priority in the user-provided VLAN is 5 the VLAN(s) applied by the IP DSLAM will also be according to this mapping value regardless what is specified in priority/innerVlanPriority. If this value is set to 255 no mapping will take place and the values specified in priority/innerVlanPriority are used. This object entry only handles priority 5. Valid from: EDA 2.1 SP1 Obsoleted from: EDA 2.2 R1A

It is possible to map the priority in a user-provided VLAN to another or the priority in the VLAN(s) applied by the IP DSLAM e.g. if the priority in the user-provided VLAN is 6 the VLAN(s) applied by the IP DSLAM will also be according to this mapping value regardless what is specified in priority/innerVlanPriority. If this value is set to 255 no mapping will take place and the values specified in priority/innerVlanPriority are used. This object entry only handles priority 6. Valid from: EDA 2.1 SP1 Obsoleted from: EDA 2.2 R1A

It is possible to map the priority in a user-provided VLAN to another or the priority in the VLAN(s) applied by the IP DSLAM e.g. if the priority in the user-provided VLAN is 7 the VLAN(s) applied by the IP DSLAM will also be according to this mapping value regardless what is specified in priority/innerVlanPriority. If this value is set to 255 no mapping will take place and the values specified in priority/innerVlanPriority are used. This object entry only handles priority 7. Valid from: EDA 2.1 SP1 Obsoleted from: EDA 2.2 R1A

A list of downstream flows that are contained in/use this PVC. Each octet is a number of a flow that exists (is active).

A list of upstream flows that are contained in/use this PVC. Each octet is a number of a flow that exists (is active).

When packets arrive on the uplink, the DSLAM needs to determine which flow the packet belongs to. This can be done in one of three ways. I.e by looking at ... classic (0) VLAN and destination MAC address. pbit (1) VLAN, destination MAC address and p-bit/CoS. dscp (2) VLAN, destination MAC address and DSCP (part of ToS). Enumeration: 'pbit': 1, 'dscp': 2, 'classic': 0.

When packets arrive on a DSL line, the DSLAM needs to determine which flow the packet belongs to. This can be done in one of four ways. I.e by looking at ... classic (0) PVC. (Only one flow may be associated with the PVC.) pbit (1) PVC and p-bit/CoS. dscp (2) PVC and DSCP (part of ToS). ethertype (3) PVC and Ethertype. Enumeration: 'ethertype': 3, 'pbit': 1, 'dscp': 2, 'classic': 0.

The DSLAM may schedule packets in this flow in competition with packets in other flows in the same PVC. none (0) There is only one flow, no scheduling needed. strictPriority (1) Strict Priority, the flow with flowIndex=0 has highest priority. deficitRoundRobin (2) Deficit Round Robin, dfcBytesPerRound determines how many bytes are sent from the flow for each turn of the Round Robin. modifiedDeficitRoundRobin (3) Modified Deficit Round Robin, the flow with flowIndex=0 has strict priority over the others. The other flows are scheduled according to DRR on what bandwidth remains. Enumeration: 'modifiedDeficitRoundRobin': 3, 'none': 0, 'strictPriority': 1, 'deficitRoundRobin': 2.

Frames received from the aggregation network will be forwarded on this PVC if the destination MAC address is unknown to the DSLAM. The frame must be received in the same VLAN as associated with the PVC. Valid from: EDA 2.1 SP2

This parameter is used to enable Layer 2 Protocol Tunneling. The tunneling mechanism is a propritary solution specified by Cisco. The Layer 2 Control Protocol tunneling feature is only available when accessMethod is transparrentLan. Customers at different sites connected across a SP network need to use various Layer 2 protocols to scale their topologies to include all remote sites, as well as the local sites. STP must run properly, and every VLAN should build a proper spanning tree that includes the local site and all remote sites across the SP network. Cisco Discovery Protocol (CDP) must discover neighboring Cisco devices from local and remote sites. VLAN Trunking Protocol (VTP) must provide consistent VLAN configuration throughout all sites in the customer network. When protocol tunneling is enabled, DSLAM on the inbound side of the SP network encapsulate Layer 2 protocol packets with a special MAC address and send them across the SP network. Core switches in the network do not process these packets but forward them as normal packets. Layer 2 protocol data units (PDUs) for CDP, STP, or VTP cross the SP network and are delivered to customer switches on the outbound side of the SP network. Identical packets are received by all customer ports on the same VLANs with these results: Users on each of a customer's sites can properly run STP, and every VLAN can build a correct spanning tree, based on parameters from all sites and not just from the local site. CDP discovers and shows information about the other Cisco devices connected through the SP network. VTP provides consistent VLAN configuration throughout the customer network, propagating to all switches through the SP. When the Layer 2 PDUs that entered the DSLAM on the inbound side, the DSLAM overwrites the customer PDU-destination MAC address with a well-known Cisco proprietary multicast address (01-00-0c-cd-cd-d0). The DSLAM on the outbound side restore the proper Layer 2 protocol and MAC address information and forward the packets to all PVCs in the same VLAN. Therefore, the Layer 2 PDUs remain intact and are delivered across the SP network to the other side of the customer network. Tunneling of Layer 2 control protocols is enabled using this bit-map. The various bit positions are: 0 stp When set Layer 2 Control Protocol tunneling is enabled for Spanning Tree Protocol (destination MAC = 01:80:c2:00:00:00) 1 pvstp When set Layer 2 Control Protocol tunneling is enabled for Per VLAN Spanning Tree Protocol, a Cisco specified extension to STP (destination MAC = 01:00:0c:cc:cc:cd). 2 cdp When set Layer 2 Control Protocol tunneling is enabled for Cisco Discovery Protocol (destination MAC = 01:00:0c:cc:cc:cc). 3 vtp When set Layer 2 Control Protocol tunneling is enabled for Virtual Trunking Protocol (destination MAC = 01:00:0c:cc:cc:cc). Valid from: EDA 2.1 SP2 Bits: 'pvstp': 1, 'cdp': 2, 'stp': 0, 'vtp': 3.

Setting this parameter to True enables the end-user to send IGMP queries and multicast streams in the VLAN associated with the PVC. Valid from: EDA 2.1 SP2

When set to clear, all the DHCP Mapping entries for this Connection will be removed from the DHCP Mapping Table. Enumeration: 'clear': 1.

If True Clear the Subscriber MAC History for this pCon(Line,Pvc). The value can be either True(1) or False(2). Default Value will be false.

A parameter which gives on which traffic the Gateway Mac filtering needs to be done. If the value is set to 0 then the only in the upstream the Gateway Mac will be filtered. If the value is set to 1 then in both upstream and down stream the Gateway Mac will be filtered. Enumeration: 'updownstream': 1, 'upstream': 0.

A parameter which gives the number of downstream frames received on the PVC per second.

A parameter which gives the number of upstream frames received on the PVC per second.

A parameter which gives the number of downstream bits received on the PVC per second.

A parameter which gives the number of upstream bits received on the PVC per second.

This parameter decides the behavior of the ArpProxy in the IP-DSLAM. It is only valid when forced forwarding is enabled (peaBridgeIpDslam::gatewayFixedForwarding set to true). The possible values are: 0 proxyAllArpRequests All ARP Requests from the end-user will always be replied with the MAC address of the default gateway configured for the end-user, except gratuitous ARP Requests which will be dropped. This setting should be used when broadcast traffic should be kept to a minimum, for instance when running large L2 networks. 1 proxyNonGwArpRequests All ARP Requests from the end-user to the default gateway are forwarded to the network. Gratuitous ARP Requests are also forwarded to the network. Any request to a non gateway IP will be replied the default gateway MAC address. This setting is needed when running 'Passive ARP Learning' in VRRP enabled routers, or other technologies where ARP from the end-users are needed. 2 proxyNonGratuitousArpRequests All ARP Requests from the end-user will be replied with the MAC address of the default gateway configured for the end-user. Except gratuitous ARP Requests which are forwarded to the network. This setting should be used when broadcast traffic should be kept to a minimum, but the ARP cache timeout in the router is too long to detect end-user MAC replacement. This option is valid from EDA 2.2 SP3. ARP Requests from the network will always be proxied back. Terminology: Gratuitous ARP Request: A gratuitous ARP Request is an ARP Request where the Sender IP address and Target IP address is the same. The ARP Requests is broadcasted to other hosts in the same layer 2 network. Hosts use this ARP Request for several reasons: 1) To detect IP address conflicts 2) To advertise the IP and MAC address to other hosts, switch's and routers Valid from: EDA 2.2 SP1 Enumeration: 'proxyNonGratuitousArpRequests': 2, 'proxyNonGwArpRequests': 1, 'proxyAllArpRequests': 0.

This parameter decides how the end-users VLAN tags should be handled. The possible values are 0 endUserVLanForward End-user VLANs are filtered according to the VLAN ID ACL and then forwarded. If the VLAN ID ACL is not defined all VLAN IDs will be allowed. 1 endUserVLanFilterRemove End-user VLANs are filtered and then removed/added Upstream traffic is first filtered according to the upstream VLAN ID ACL and then the VLAN is removed. On downstream traffic the VLAN is added to the frame before sending it to the end-user. The VLAN that is added is the first VLAN in the first range specified in the downstream VLAN ID ACL. Note: For this functionality to work it is required that vlanFilter is set to allow Q-Tagged traffic Valid from: EDA 2.2 SP2 Enumeration: 'endUserVLanFilterRemove': 1, 'endUserVLanForward': 0.

Defines the VLAN ID a user is allowed to use on upstream traffic. The upstream traffic passes a VLAN ID filter and if the outermost VLAN ID in the received packet is not allowed the packet is discarded. The value can be between 0 and 4095. This parameter is only valid if endUserVlanOperation is set to endUserVLanFilterRemove. This parameter is deprecated. Please use peaBridgeIpDslam::vlanIdAclTable instead. Valid from: EDA 2.2 SP2 Deprecated from: EDA 2.2 R3A

Detemines which version of the IP filter to use for the specific PVC. 1 - pvcFilter = Use filters defined in pvcFiltersTable. 2 - accessControlList = Use Access Control List. Valid from: EDA 2.2 SP2 Enumeration: 'accessControlList': 2, 'pvcFilter': 1.

Setting this value to non-zero will specify the VLAN ID ACL to be used in the upstream direction. The value of zero means no VLAN ID ACL is used for this PVC. Default value will be zero Valid from: EDA 2.2 R3A

Setting this value to non-zero will specify the VLAN ID ACL to be used in the downstream direction. The value of zero means no VLAN ID ACL is used for this PVC. Default value will be zero Valid from: EDA 2.2 R3A

Setting this value to non-zero will specify the EtherType ACL to be used in the upstream direction. The value of zero means no EtherType ACL is used for this PVC. Default value will be zero Valid from: EDA 2.2 SP2

Setting this value to non-zero will specify the EtherType ACL to be used in the downstream direction. The value of zero means no EtherType ACL is used for this PVC. Default value will be zero Valid from: EDA 2.2 SP2

Setting this value to non-zero will specify the IP ACL to be used in the upstream direction. The value of zero means no IP ACL is used for this PVC. Default value will be zero Valid from: EDA 2.2 SP2

Setting this value to non-zero will specify the IP ACL to be used in the downstream direction. The value of zero means no IP ACL is used for this PVC. Default value will be zero Valid from: EDA 2.2 SP2

Use this parameter to convert the end-users DHCP messages from broadcast to unicast. This is very usefull when trying to minimise the amount of broadcast in a L2 network. When the IP-DSLAM receives a DHCP Discover or a Request it will change the destination MAC address from the broadcast address to the configured DHCP Server Mac Address (This parameter). - To enable the functionality add the MAC address of the DHCP server (To configure 00-80-03-04-05-06 add 0x00 0x80 0x03 0x04 0x05 0x06) - To disable the functionality add MAC address 00-00-00-00-00-00 Note: When using this function the end-user will no longer be able to select between different DHCP servers. This functionality is only valid if accessMethod is set to 'dhcp' or 'dhcpIpoa'. Valid from: EDA 2.2 R3A

Determines whether MAC and IP address validation is performed when a subscriber sends multicast frames upstream in the network. Example: If a subscriber is configured to access method DHCP and anonymous multicast subscriber is allowed for that subscriber, it is not validated that the subscriber has been assigned an IP address via DHCP, when the subscriber tries to join a multicast group. The possible values are TRUE (1) - Subscriber source IP and MAC addresses are not validated. FALSE(2) - Subscriber source IP and MAC addresses are validated. Valid from: EDA 2.2 SP3

A list of entries to the PVCs.

An entry containing the filters for a PVC for the subscriber line identified by lineIndex.

The filter type can be positive(0) or negative(1). If positive all packets with EthernetType which are part of the filter entries are allowed by the filter. If negative the filter allows all packets except the packets with the EthernetType which are part of the filter entries. If no entries are specified, all types are allowed. When pvcFilterVersion is AccessControlList the upsteamEthernetTypesFilterType is determined by the EthernetType and MatchAction specified in the ACL Rules. This parameter is deprecated. Please use the Ethernet Type Access Control List instead. For more information please see the following parameters: peaBridgeIpDslam::pvcUpstreamEtherTypeAclId peaBridgeIpDslam::etherTypeAclTable peaBridgeIpDslam::etherTypeAclRuleTable Deprecated from: EDA 2.2 SP3 Enumeration: 'positive': 0, 'negative': 1.

Filter on Ethernet Type in packets from subscriber into network. A list of EthernetType entries, each two byte in network byte order (big endian). Example: EthernetTypeIp=0x800 => '0x08 0x00' This parameter is deprecated. Please use the Ethernet Type Access Control List instead. For more information please see the following parameters: peaBridgeIpDslam::pvcUpstreamEtherTypeAclId peaBridgeIpDslam::etherTypeAclTable peaBridgeIpDslam::etherTypeAclRuleTable Deprecated from: EDA 2.2 SP3

The filter type can be positive(0) or negative (1). If positive all packets with the destination IP which are part of the filter entries are allowed by the filter. If negative the filter allows all packets except the packets with the destination IP which are part of the filter entries. This parameter is deprecated. Please use the IP Access Control List instead. For more information please see the following parameters: peaBridgeIpDslam::pvcUpstreamIpAclId peaBridgeIpDslam::ipAclTable peaBridgeIpDslam::ipAclRuleTable Deprecated from: EDA 2.2 SP3 Enumeration: 'positive': 0, 'negative': 1.

Filter on destination IP in packets from subscriber into network. Filter entries 8 bytes each, representing a range - to represent the range >=10.0.0.0 <=16.0.0.0 add 0x0a 0x00 0x00 0x00 0x10 0x00 0x00 0x00 This parameter is deprecated. Please use the IP Access Control List instead. For more information please see the following parameters: peaBridgeIpDslam::pvcUpstreamIpAclId peaBridgeIpDslam::ipAclTable peaBridgeIpDslam::ipAclRuleTable Deprecated from: EDA 2.2 SP3

The filter type is negative (1). The filter allows all packets except the packets with the IP source port number which are part of the filter entries. This parameter is deprecated. Please use the IP Access Control List instead. For more information please see the following parameters: peaBridgeIpDslam::pvcUpstreamIpAclId peaBridgeIpDslam::ipAclTable peaBridgeIpDslam::ipAclRuleTable Deprecated from: EDA 2.2 SP3 Enumeration: 'negative': 1.

Filter on IP source port number in packets from subscriber into network. Filter entries 2 bytes each - to exclude FTP add 21 = 0x00 0x15 This parameter is deprecated. Please use the IP Access Control List instead. For more information please see the following parameters: peaBridgeIpDslam::pvcUpstreamIpAclId peaBridgeIpDslam::ipAclTable peaBridgeIpDslam::ipAclRuleTable Deprecated from: EDA 2.2 SP3

The filter type is negative (1). The filter allows all packets except the packets with the IP destination port number which are part of the filter entries. This parameter is deprecated. Please use the IP Access Control List instead. For more information please see the following parameters: peaBridgeIpDslam::pvcUpstreamIpAclId peaBridgeIpDslam::ipAclTable peaBridgeIpDslam::ipAclRuleTable Deprecated from: EDA 2.2 SP3 Enumeration: 'negative': 1.

Filter on IP destination port number in packets from subscriber into network. Filter entries 2 bytes each - to exclude FTP add 21 = 0x00 0x15 This parameter is deprecated. Please use the IP Access Control List instead. For more information please see the following parameters: peaBridgeIpDslam::pvcUpstreamIpAclId peaBridgeIpDslam::ipAclTable peaBridgeIpDslam::ipAclRuleTable Deprecated from: EDA 2.2 SP3

The filter type can be positive(0) or negative(1). If positive all packets with EthernetType which are part of the filter entries are allowed by the filter. If negative the filter allows all packets except the packets with the EthernetType which are part of the filter entries. If no entries are specified, all types are allowed. When pvcFilterVersion is AccessControlList the downsteamEthernetTypesFilterType is determined by the EthernetType and MatchAction specified in the ACL Rules. This parameter is deprecated. Please use the Ethernet Type Access Control List instead. For more information please see the following parameters: peaBridgeIpDslam::pvcDownstreamEtherTypeAclId peaBridgeIpDslam::etherTypeAclTable peaBridgeIpDslam::etherTypeAclRuleTable Deprecated from: EDA 2.2 SP3 Enumeration: 'positive': 0, 'negative': 1.

Filter on Ethernet Type in packets from network to subscriber. A list of EthernetType entries, each two byte in network byte order (big endian). Example: EthernetTypeIp=0x800 => '0x08 0x00' This parameter is deprecated. Please use the Ethernet Type Access Control List instead. For more information please see the following parameters: peaBridgeIpDslam::pvcDownstreamEtherTypeAclId peaBridgeIpDslam::etherTypeAclTable peaBridgeIpDslam::etherTypeAclRuleTable Deprecated from: EDA 2.2 SP3

The filter type can be positive(0) or negative (1). If positive all packets with the source IP which are part of the filter entries are allowed by the filter. If negative the filter allows all packets except the packets with the source IP which are part of the filter entries. This parameter is deprecated. Please use the IP Access Control List instead. For more information please see the following parameters: peaBridgeIpDslam::pvcDownstreamIpAclId peaBridgeIpDslam::ipAclTable peaBridgeIpDslam::ipAclRuleTable Deprecated from: EDA 2.2 SP3 Enumeration: 'positive': 0, 'negative': 1.

Filter on source IP in packets from network to subscriber. Filter entries 4 bytes each, representing a single address. To represent the adress 10.0.0.0 add 0x0a 0x00 0x00 0x00 This parameter is deprecated. Please use the IP Access Control List instead. For more information please see the following parameters: peaBridgeIpDslam::pvcDownstreamIpAclId peaBridgeIpDslam::ipAclTable peaBridgeIpDslam::ipAclRuleTable Deprecated from: EDA 2.2 SP3

The filter type is negative (1). The filter allows all packets except the packets with the IP source port number which are part of the filter entries. This parameter is deprecated. Please use the IP Access Control List instead. For more information please see the following parameters: peaBridgeIpDslam::pvcDownstreamIpAclId peaBridgeIpDslam::ipAclTable peaBridgeIpDslam::ipAclRuleTable Deprecated from: EDA 2.2 SP3 Enumeration: 'negative': 1.

Filter on IP source port number in packets from network to subscriber. Filter entries 2 bytes each - to exclude FTP add 21 = 0x00 0x15 This parameter is deprecated. Please use the IP Access Control List instead. For more information please see the following parameters: peaBridgeIpDslam::pvcDownstreamIpAclId peaBridgeIpDslam::ipAclTable peaBridgeIpDslam::ipAclRuleTable Deprecated from: EDA 2.2 SP3

The filter type is negative (1). The filter allows all packets except the packets with the IP destination port number which are part of the filter entries. This parameter is deprecated. Please use the IP Access Control List instead. For more information please see the following parameters: peaBridgeIpDslam::pvcDownstreamIpAclId peaBridgeIpDslam::ipAclTable peaBridgeIpDslam::ipAclRuleTable Deprecated from: EDA 2.2 SP3 Enumeration: 'negative': 1.

Filter on IP destination port number in packets from network to subscriber. Filter entries 2 bytes each - to exclude FTP add 21 = 0x00 0x15 This parameter is deprecated. Please use the IP Access Control List instead. For more information please see the following parameters: peaBridgeIpDslam::pvcDownstreamIpAclId peaBridgeIpDslam::ipAclTable peaBridgeIpDslam::ipAclRuleTable Deprecated from: EDA 2.2 SP3

The filter type is positive(0). All packets with the MAC addresses which are part of the filter entries are allowed by the filter. Enumeration: 'positive': 0.

Filter on subscriber MAC addresses. At least one entry should apply here if DHCP is not used. Filter entries 6 bytes each - to include 00-80-03-04-05-06 add 0x00 0x80 0x03 0x04 0x05 0x06

The subscriber IP filter type can be either positive(0) or disabled(2). If positive all packets with the subscriber IP which are part of the filter entries are allowed by the filter. If disabled no filtering will be done on subscriber IP addresses and all packets will pass the filter. This parameter is deprecated. Please use peaBridgeIpDslam::subsIpFilterType instead. Deprecated from: EDA 2.2 R3A Enumeration: 'disabled': 2, 'positive': 0.

Filter on subscriber IP addresses. When using DHCP the entries in the filter are added automatically according to the DHCP leases. For other access methods IP addresses can be added for filtering purposes. Filter entries are 4 bytes each. - to include 10.2.3.4 add 0x0a 0x02 0x03 0x04 This parameter is deprecated. Please use the peaBridgeIpDslam::subsIpFilterTable table instead. Deprecated from: EDA 2.2 R3A

Filter on TCP/UDP destination port number as well as destination IP address in packets from subscriber into network. Filter entries are 10 bytes each. The first two bytes represent the port number and the ending 8 bytes of the entry represent an IP address range. To exclude all SMTP traffic (port 25) except traffic with destination IP address in the range 10.0.0.0 to 10.0.0.10 add 0x00 0x19 0x0A 0x00 0x00 0x00 0x0A 0x00 0x00 0x0A. This parameter is deprecated. Please use the IP Access Control List instead. For more information please see the following parameters: peaBridgeIpDslam::pvcUpstreamIpAclId peaBridgeIpDslam::ipAclTable peaBridgeIpDslam::ipAclRuleTable Deprecated from: EDA 2.2 SP3

The virtual Mac address domain specifies 6 of the 8 bits in the first byte in the virtual Mac address. (The remaining two bits are the multicast bit and the globally/locally administrated bits which equals 01 to identify the locally administrated unicast address known as the virtual Mac address) With the domain bits, it is possible to secure the uniqueness of Mac addresses using different virtual Mac address schemes.

MaximumEthernetFrameSize specifies the maximum frame size that the IP DSLAM will send up-stream in the access network. Longer frames will be discarded! The specified size covers the whole frame, including Ethernet header, VLAN-tag(s) and 4 bytes of CRC. (See also the counter: DiscardedOversizedFrames.)

A list of entries to the Line Table.

An entry containing Line objects for the subscriber line identified by lineIndex.

Enable of ILMI Auto Configuration for the Line. If True, ILMI AC will try to configure the CPE with all existing PVC:s for the line.

Broadcast Storm Control (BSC) function. The threshold is set using broadcastStormControlThreshold. The function is default disabled. The possible values are 0 - BSC is disabled. 1 - BSC is enabled - broadcast is limited to broadcastStormControlThreshold. Valid from: EDA 4.0 R1A Enumeration: 'limitToThreshold': 1, 'disable': 0.

When broadcastStormControlThreshold is passed and broadcastStormControl is enabled, all broadcast traffic is limited to broadcastStormControlThreshold. Broadcast traffic above broadcastStormControlThreshold is dropped. Default is 10. Valid from: EDA 4.0 R1A

Multicast Storm Control (MSC) function. The threshold is set using multicastStormControlThreshold. The function is default disabled. The possible values are 0 - MSC is disabled. 1 - MSC is enabled - multicast is limited to multicastStormControlThreshold. Valid from: EDA 4.0 R1A Enumeration: 'limitToThreshold': 1, 'disable': 0.

When multicastStormControlThreshold is passed and multicastStormControl is enabled, all multicast traffic is limited to multicastStormControlThreshold. Multicast traffic above multicastStormControlThreshold is dropped. Default is 10. Valid from: EDA 4.0 R1A

The virtual Mac address Node ID specifies the last 3 bytes in the virtual Mac address. With the Node ID, it is possible to identify the origin of an ethernet frame, even when the IP DSLAM has been exhanged with a new IP DSLAM, with a new Mac address.

If 1, VLAN tagging is single. If 2, VLAN tagging is double. Valid from: EDA 2.0SP2 Enumeration: 'single': 1, 'qinq': 2.

The virtual Mac address 'Node ID Extended' specifies 26 bits in the virtual Mac address. With the Node ID Extended, it is possible to identify the origin of an ethernet frame, even when the IP DSLAM has been exhanged with a new IP DSLAM, with a new Mac address. From the virtualMacAddressNodeIdEx, the first 26 bits is used as shown here with X: XXXXXXXX XXXXXXXX XXXXXXXX XX000000, the unused bits are set to zero. The Node Id Extended is inserted in the Virtual MAC address, as shown here with X: ******** ******** XXXXXXXX XXXXXXXX XXXXXXXX XX******.

IP address inserted in the relay agent information when remoteIdEda is used (see 'relayAgentConfiguration' description). Zero must be used when the IP-DSLAM is running standalone, in this case the IP-DSLAM will insert its own IP address into the relay agent information. If the IP-DSLAM is not running standalone the IP address of the controlling node (e.g. EAN or MSAN) must be specified with this object.

Specifies the NodeId inserted in the relay agent information when remoteEdaId is used (see 'relayAgentConfiguration' description). The layout of the NodeId field is dependant on the IP-DSLAM configuration. Layout of relayAgentEdaNodeId when the IP-DSLAM is running standalone: | MSB LSB | | 8-bit | 8-bit | 8-bit | 8-bit | ----------------------------------------------------- | 0 | 0 | 0 | 0 | ----------------------------------------------------- | NA | NA | NA | Line | Layout of relayAgentEdaNodeId when the IP-DSLAM is located under an EAN: | MSB LSB | | 8-bit | 8-bit | 8-bit | 8-bit | ----------------------------------------------------- | 0-8 | 1-24 | 1-24 | 0 | ----------------------------------------------------- | ExtNo | PortLevel1 | PortLevel2 | Line | Layout of relayAgentEdaNodeId when the IP-DSLAM is located under an MSAN: | MSB LSB | | 8-bit | 8-bit | 8-bit | 8-bit | ----------------------------------------------------- | 1-20 | 1-30 | 0 | 0 | ----------------------------------------------------- | SubRack | Slot | Reserved | Line | The field 'Line' is and offset to which the IP-DSLAM will add the actual line number in the relay agent information. Care must be taken to ensure that the specified offset + actual line number does not exceed 255.

Unique number assigned to each flow within PVC. The highest index is 7 upstream and 3 downstream. Please note that flowIndex affects priority scheduling and buffer arbitration. Even when DRR scheduling is requested, flowIndex determines probability of packets being discarded from queue during congestion. Higher flowIndex means higher probability of being discarded. Range 0-3 downstream, 0-7 upstream. In the upstream direction flowIndex is the outgoing p-bit value, with exception for the case that all p-bit values are collected in one flow, in which case the flowIndex value is 0.

A list of downstream flows

An entry containing flows identified by lineIndex, pvcIndex and flowIndex.

What values (in CoS or DSCP field) signal that the packet belongs to this flow. One octet per value. A packet that contains one of these values is classified as belonging to this flow.

Is this flow to be policed?

The maximum allowed average information rate in the flow. The rate must be lower than or equal to the configured ADSL rate and in steps of 32000 bps. Notice: To carry telephony over IP, 192000 bps is needed and the ADSL line must be configured to at least 192000.

The maximum number of bytes in a burst. Notice: To allow a complete telephony over IP packet to be included in one burst, 250 bytes are needed. Furthermore, if a VBR service category has been chosen, this parameter cannot be 0.

The DRR scheduling algorithm visits all the queues in the PVC in a circular fashion (round robin). For each turn of the circle it transfers dfcBytesPerRound bytes from this queue to the (HW) transmit queue.

The maximum number of packet buffers allowed to be placed in queue for one downstream flow queue

Statistics information for a list of downstream flows

An entry containing flows identified by lineIndex, pvcIndex and flowIndex.

The number of packets that have been discarded by the policing mechanism.

The number of Ethernet frames that have passed.

The number of bytes that have passed.

The number of bytes that have been discarded by the policing mechanism.

The maximum number of buffers stored in a downstream flow queue at any time since the counter was reset. Zero is the only value that can be written to dfsMaxQueueUsage to clear the counter. Valid from: EDA 2.2 R3A

A list of upstream flows

An entry containing flows identified by lineIndex, pvcIndex and flowIndex.

What values (in CoS or DSCP field) signal that the packet belongs to this flow. One octet per value. A packet that contains one of these values is classified as belonging to this flow.

Is this flow to be policed?

The maximum allowed average data rate in the flow. The rate must be lower than or equal to the configured ADSL rate and in steps of 32000 bps. Notice: To carry telephony over IP, 192000 bps is needed and the ADSL line must be configured to at least 192000.

The maximum number of bytes in a burst. Notice: To allow a complete telephony over IP packet to be included in one burst, 250 bytes are needed. Furthermore, if a VBR service category has been chosen, this parameter cannot be 0.

Is the CoS/p-bit value in the Ethernet header to be overwritten? This MIB object may be removed. Obsoleted from: EDA 2.2 SP1

One Flow has one VLAN priority value associated, that VLAN priority value will be written in the outer most VLAN tag of the Ethernet frame before the Ethernet frame is forwarded to the aggregation network. Traffic within the policed bandwidth is forwarded to the aggregation network while traffic exceeding the policed bandwidth is either dropped or remarked with another VLAN priority. The ufcExceedingTrafficFlow parameter is used to configure whether traffic exceeding the policed bandwidth should be dropped or remarked with another VLAN priority before forwarding the packet to the aggregation network. Remarking of traffic is done by redirecting traffic exceeding the policed bandwidth of the current flow to another flow as illustrated below. IP DSLAM _______________________________________________________________ | _________________ | | ( ) | | /<--- ( Flow x policing ) <----\ | | / (_________________) \ | | / | \ | | / | Remark / redirect \ | | / | exceeding traffic \ | | / | \ | | / __V______________ _\____________ | Aggregation |/ ( ) ( Initial ) | Network <----|<----------- ( Flow y policing ) <--------( flow )<----|---- End-user |\ (_________________) (___selection__) | | \ | / | | \ | Remark / redirect / | | \ | exceeding traffic / | | \ | / | | \ __V______________ / | | \ ( ) / | | \<--- ( Flow y policing ) <----/ | | (_________________) | | | | | | | | X Discard exceeding traffic | |_______________________________________________________________| Set ufcExceedingTrafficFlow to zero to drop traffic exceeding the policed bandwidth rate for the flow. Set ufcExceedingTrafficFlow to a value in the range 1..8 to redirect excess traffic to another flow. The value written to ufcExceedingTrafficFlow is the flowIndex of the flow where traffic must be redirected to. ufcExceedingTrafficFlow can not be set to the same value as the flowIndex of the current flow. Note: Care must be taken to not configure an infinite redirect loop. Valid from: EDA 2.2 R3A

Statistics information for a list of upstream flows

An entry containing flows identified by lineIndex, pvcIndex and flowIndex.

The number of packets that have been discarded by the policing mechanism.

The number of Ethernet frames that have passed.

The number of bytes that have passed.

The number of bytes that have been discarded by the policing mechanism.

A list of entries to the multicast filter type list.

The lineIndex and pvcIndex pair forms a unique identification of a PVC in the managed device. A mcastFilterTypeEntry contains multicast filter type information for a PVC.

Specifies whether the multicast filter is positive or negative. If the multicast filter is positive, the managed device is allowed to forward multicast group Internet addresses specified in mcastFilterTable. If the multicast filter is negative, the managed device is allowed to forward all multicast group Internet addresses except the ones specified in mcastFilterTable. Whether the multicast filter is positive or negative is specified per PVC. Enumeration: 'positive': 0, 'negative': 1.

A list of entries to the multicast filter list.

The lineIndex and pvcIndex pair forms a unique identification of a PVC in the managed device. A mcastFilterEntry contains multicast filter information for a PVC. Each entry describes a range of consecutive multicast group addresses which are allowed or disallowed, depending on the value of mcastFilterType,to be forwarded on the PVC. If the multicast filter is empty, then all the multicast groups are allowed irrespective of mcastFilterType. F.ex. if multicast group Internet addresses in the range 224.10.10.10 to 224.10.10.40 are allowed to be forwarded on the PVC, a positive (0) multicast filter should be used, mcastFilterFirstAddress is set to 224.10.10.10 and mcastFilterLastAddress is set to 224.10.10.40. Multiple entries may be required to describe the complete multicast filter for one PVC.

The type of Internet address used in the multicast filter address range.

The first address in the multicast group Internet address range. The type of this address is determined by the value of the mcastFilterAddressType object. The mcastFilterFirstAddress may not be empty due to the SIZE restriction.

The last address in the multicast group Internet address range. The type of this address is determined by the value of the mcastFilterAddressType object. mcastFilterLastAddress must be a equal to or higher than mcastFilterFirstAddress before the settings are put into operation. The mcastFilterFirstAddress may not be empty due to the SIZE restriction. To modify the value of mcastFilterLastAddress, the conceptual row must be taken Out of Service

The Vlan ID to be used for the multicast traffic on a multicast group Internet address range, from and to the specified PVC. The value -1 is a nil-value indicating that the outer service VLAN ID (peaBridgeIpDslam::vlanID) is used for the multicast traffic. If the mcastFilterType is 'negative' this parameter has no effect, in this case the outer service VLAN ID is always used. Valid from: EDA 2.2 SP3

The priority (accordingly to 802.1Q) that should be used for the multicast frames to and from the specified PVC. The value can be between 0 and 7 (where 7 is the highest priority). The value -1 is a nil-value indicating that the outer service VLAN priority (peaBridgeIpDslam::priority) is used for the multicast traffic. If the mcastFilterType is negative this parameter has no effect, in this case the outer service VLAN priority is always used. Valid from: EDA 2.2 SP3

The mcastFilterRowStatus is used to manage the creation and deletion of rows in mcastFilterTable.

A list of MAC address entries of Subscribers disconnected/connected to IP DSLAM

An entry containing the Subscriber MAC address for each connection identified by the lineIndex and pvcIndex.

MAC address of the subscriber.

The timestamp which indicates the time when the Subscriber MAC address was last seen.

If Active indicates that the subscriber is currently connected and Inactive shows the MAC of a disconnected subscriber. The value can be either Active(1) or Inactive(0). Enumeration: 'active': 1, 'inactive': 0.

macFilterAgedTime specifies in seconds the maximum age of inactive MAC address entries in the subscriber MAC filter for access methods PPPoE and TLS.

This table maintains a list of VLAN ID Access Control Lists in the IPDSLAM. Each Access Control List is made up of a group of access rules. The access rules are stored in the vlanIdAclRuleTable. This table is used to add/delete VLAN ID Access Control Lists. ACL's are statements which are called rules of ACL that are grouped together by a number. Within this group of statements, when a packet is processed by an ACL on the IPDSLAM, the IPDSLAM will go through certain steps in finding a match against the ACL statements. ACL's are processed top-down by the IPDSLAM. Using a top-down approach, a packet is compared to the first statement in the ACL, and if the IPDSLAM finds a match between the packet and the statement, the IPDSLAM will execute one of two actions included with the statement: - Permit - Deny If the IPDSLAM doesn't find a match of packet contents to the first ACL statement, the IPDSLAM will proceed to the next statement in the list, again going through the same matching process If there isn't a match on this statement, the IPDSLAM will keep on going through the list until it finds a match. If the IPDSLAM goes through the entire list and doesn't find a match, the IPDSLAM will drop the packet. If there is a match on a statement, no further statements are processed. Therefore, the order of the statements is very important in an ACL. Valid from: EDA 2.2 R3A

An entry in the vlanIdAclTable. Valid from: EDA 2.2 R3A

Index of the VLAN ID Access Control List. Valid from: EDA 2.2 R3A

Total number of rules in the VLAN ID Access Control List (ACL). Valid from: EDA 2.2 R3A

This object is used to manage the creation, deletion and modification of rows in the VLAN ID Access Control List Table. Due to the way SNMP is handled in the IPDSLAM and the configuration file verification, RowStatus is handled slightly different in the IPDSLAM compared to the way described in RFC 2579. Below is a state/event table describing how the RowStatus will be handled in the IPDSLAM. The action to take and the return value assumes that the index to the table is valid. +-------------+---------------+---------------+---------------+---------------+ | Command | A | B | C | D | | | status column | status column | status column | status column | | |does not exist | notReady | notInService | is active | +-------------+---------------+---------------+---------------+---------------+ | Set status | Inconsistent | | Inconsistent | Inconsistent | | column | Value | | Value | Value | | to | (1) | (9) | (1) | (1) | | CreateAndGo | State = A | | State = C | State = D | +-------------+---------------+---------------+---------------+---------------+ | Set status | NoError | | NoError | NoError | | column to | (2) | (9) | (2) | (2)(3) | |CreateAndWait| State = C | | State = C | State = C | +-------------+---------------+---------------+---------------+---------------+ | Set status | Inconsistent | | NoError | NoError | | to | Value | | | | | | (4) | (9) | (5) | | | Active | State = A | | State = D | State = D | +-------------+---------------+---------------+---------------+---------------+ | Set status | Inconsistent | | NoError | NoError | | column Value| | | | | | to | (4) | (9) | | (6) | | NotInService| State = A | | State = C | State = C | +-------------+---------------+---------------+---------------+---------------+ | Set status | Inconsistent | Inconsistent | Inconsistent | Inconsistent | | column | Value | Value | Value | Value | | to | | | | | | NotReady | State = A | State = B | State = C | state = D | +-------------+---------------+---------------+---------------+---------------+ | Set status | NoError | | NoError | NoError | | column | | | | | | to | | (9) | (7) | (7) | | Destroy | State = A | | State = A | State = A | +-------------+---------------+---------------+---------------+---------------+ | Get | NoSuchInstance| | NoError | NoError | | any column | (4) | (9) | (8) | (8) | | value | State = A | | State = C | State = D | +-------------+---------------+---------------+---------------+---------------+ (1) CreateAndGo is not supported in the IPDSLAM because the application receiving the command does not receive all parameters for the conceptual row in the table simultaneously but as a series of commands. (2) Temporary instance of the conceptual row is created for the Management, and placed in state NotInService. (3) If an instance of the conceptual row exists in Runtime, then copy it to the temporary instance. (4) The instance of the conceptual row does not exist in the Management and Runtime. (5) Data from the temporary instance of the conceptual row is copied to the runtime instance and the conceptual row is set to state Active. The temporary instance is deleted. (6) Temporary instance of the conceptual row is created for the Management, and placed in state NotInService. Data from the runtime instance of the conceptual row is copied to the temporary instance and the runtime instance is deleted. (7) The conceptual row may exist is two instances, a temporary management instance and a runtime instance. - Loop through all the connections and find for which connections ACL is being used - If the ACL is not used for any connection, then delete ACL (the management and runtime instance), otherwise return SnmpError. (8) If a temporary management instance of the row exists, then the read operation returns the variable value from that instance, otherwise the returned value is taken from the runtime instance. (9) The conceptual row will never exist in notReady state Valid from: EDA 2.2 R3A

This table is used to add/delete individual access rule statement in an VLAN ID Access Control List. The order of the rules is very important. The rules are processed in a top down order. Once a match is found, no further rules are processed. If no match is found, the packet is dropped. Valid from: EDA 2.2 R3A

An entry in the VLAN ID ACL Rule Table. Valid from: EDA 2.2 R3A

The Access Control List may have multiple rules. The vlanIdAclRuleIndex specifies the position of the particular rule in the ACL. Valid from: EDA 2.2 R3A

Indicates the action to be taken when packet meets the filtering condition in an ACL Rule. permit: Every packet that matches rule condition is forwarded for further processing. deny: Every packet that matches rule condition is discarded. The value cannot be changed while the Rule is Active. Valid from: EDA 2.2 R3A Enumeration: 'deny': 0, 'permit': 1.

vlanIdAclVlanIdMin is 12 bit VLAN ID (0 to 4095) which defines the first element of the intended VLAN ID range. vlanIdAclVlanIdMin and vlanIdAclVlanIdMax together indicate a range of VLAN IDs. Packets from the host with a VLAN ID in the specified range will be filtered, depending on the value of the action field. The value cannot be changed while the rule is active. The default value is 0. Valid from: EDA 2.2 R3A

vlanIdAclVlanIdMax is 12 bit VLAN ID (0 to 4095) which defines the last element of the intended VLAN ID range. vlanIdAclVlanIdMin and vlanIdAclVlanIdMax together indicate a range of VLAN IDs. Packets from the host with a VLAN ID in the specified range will be filtered, depending on the value of the action field. The value cannot be changed while the rule is active. The default value is 4095. Valid from: EDA 2.2 R3A

This object is used to manage creation, deletion and modification of rows in the Access Control List Rule Table. Due to the way SNMP is handled in the IPDSLAM and the configuration file verification, RowStatus is handled slightly different in the IPDSLAM compared to the way described in RFC 2579. Below is a state/event table describing how the RowStatus will be handled in the IPDSLAM. The action to take and the return value assumes that the index to the table is valid. +-------------+---------------+---------------+---------------+---------------+ | Command | A | B | C | D | | | status column | status column | status column | status column | | |does not exist | notReady | notInService | is active | +-------------+---------------+---------------+---------------+---------------+ | Set status | Inconsistent | | Inconsistent | Inconsistent | | column | Value | | Value | Value | | to | (1) | (10) | (1) | (1) | | CreateAndGo | State = A | | State = C | State = D | +-------------+---------------+---------------+---------------+---------------+ | Set status | NoError | | NoError | NoError | | column to | (2) | (10) | (2) | (2)(3) | |CreateAndWait| State = C | | State = C | State = C | +-------------+---------------+---------------+---------------+---------------+ | Set status | Inconsistent | | NoError | NoError | | to | Value | | | | | | (4) | (10) | (5) | | | Active | State = A | | State = D | State = D | +-------------+---------------+---------------+---------------+---------------+ | Set status | Inconsistent | | NoError | NoError | | column | Value | | | | | to | (4) | (10) | | (6) | | NotInService| State = A | | State = C | State = C | +-------------+---------------+---------------+---------------+---------------+ | Set status | Inconsistent | Inconsistent | Inconsistent | Inconsistent | | column | Value | Value | Value | Value | | to | | | | | | NotReady | State = A | State = B | State = C | state = D | +-------------+---------------+---------------+---------------+---------------+ | Set status | NoError | | NoError | NoError | | column | | | | | | to | | (10) | (7) | (7) | | Destroy | State = A | | State = A | State = A | +-------------+---------------+---------------+---------------+---------------+ |Set any other| Inconsistent | | NoError | Inconsistent | |column to | Name | (10) | | Value | |some value | (4) | | | (8) | | | State = A | | State = C | State = D | +-------------+---------------+---------------+---------------+---------------+ | Get | NoSuchInstance| | NoError | NoError | | any column | (4) | (10) | (9) | (9) | | value | State = A | | State = C | State = D | +-------------+---------------+---------------+---------------+---------------+ (1) CreateAndGo is not supported in the IPDSLAM because the application receiving the command does not receive all parameters for the conceptual row in the table simultaneously but as a series of commands. (2) Temporary instance of the conceptual row is created for the management and placed in state NotInService. (3) If an instance of the conceptual row exists in runtime, it is copied to the temporary instance. (4) The instance of the conceptual row does not exists in management and runtime. (5) Data from the temporary instance of the conceptual row is copied to the runtime instance and the conceptual row is set to state Active. The temporary instance is deleted. (6) Temporary instance of the conceptual row is created in the management and placed in state NotInService. Data from the runtime instance of the conceptual row is copied to the temporary instance and the runtime instance is deleted. (7) The conceptual row may exist is two instances, a temporary management instance and a runtime instance. Both instances are deleted. (8) The ACL rule cannot be edited when conceptual row is Active. (9) If a temporary management instance of the row exists, then the read operation returns the variable value from that instance, otherwise the returned value is taken from the runtime instance. (10) The conceptual row can never exist in state notReady. Valid from: EDA 2.2 R3A

This table maintains a list of EtherType Access Control Lists in the IPDSLAM. Each Access Control List is made up of a group of access rules. The access rules are stored in the etherTypeAclRuleTable. This table is used to add/delete EtherType Access Control Lists. ACL's are statements which are called rules of ACL that are grouped together by a number. Within this group of statements, when a packet is processed by an ACL on the IPDSLAM, the IPDSLAM will go through certain steps in finding a match against the ACL statements. ACL's are processed top-down by the IPDSLAM. Using a top-down approach, a packet is compared to the first statement in the ACL, and if the IPDSLAM finds a match between the packet and the statement, the IPDSLAM will execute one of two actions included with the statement: - Permit - Deny If the IPDSLAM doesn't find a match of packet contents to the first ACL statement, the IPDSLAM will proceed to the next statement in the list, again going through the same matching process If there isn't a match on this statement, the IPDSLAM will keep on going through the list until it finds a match. If the IPDSLAM goes through the entire list and doesn't find a match, the IPDSLAM will drop the packet. If there is a match on a statement, no further statements are processed. Therefore, the order of the statements is very important in an ACL. Valid from: EDA 2.2 SP2

An entry in the etherTypeAclTable. Valid from: EDA 2.2 SP2

Index of the EtherType Access Control List. Valid from: EDA 2.2 SP2

Total number of rules in the EtherType Access Control List (ACL). Valid from: EDA 2.2 SP2

This object is used to manage the creation, deletion and modification of rows in the EtherType Access Control List Table. Due to the way SNMP is handled in the IPDSLAM and the configuration file verification, RowStatus is handled slightly different in the IPDSLAM compared to the way described in RFC 2579. Below is a state/event table describing how the RowStatus will be handled in the IPDSLAM. The action to take and the return value assumes that the index to the table is valid. +-------------+---------------+---------------+---------------+---------------+ | Command | A | B | C | D | | | status column | status column | status column | status column | | |does not exist | notReady | notInService | is active | +-------------+---------------+---------------+---------------+---------------+ | Set status | Inconsistent | | Inconsistent | Inconsistent | | column | Value | | Value | Value | | to | (1) | (9) | (1) | (1) | | CreateAndGo | State = A | | State = C | State = D | +-------------+---------------+---------------+---------------+---------------+ | Set status | NoError | | NoError | NoError | | column to | (2) | (9) | (2) | (2)(3) | |CreateAndWait| State = C | | State = C | State = C | +-------------+---------------+---------------+---------------+---------------+ | Set status | Inconsistent | | NoError | NoError | | to | Value | | | | | | (4) | (9) | (5) | | | Active | State = A | | State = D | State = D | +-------------+---------------+---------------+---------------+---------------+ | Set status | Inconsistent | | NoError | NoError | | column Value| | | | | | to | (4) | (9) | | (6) | | NotInService| State = A | | State = C | State = C | +-------------+---------------+---------------+---------------+---------------+ | Set status | Inconsistent | Inconsistent | Inconsistent | Inconsistent | | column | Value | Value | Value | Value | | to | | | | | | NotReady | State = A | State = B | State = C | state = D | +-------------+---------------+---------------+---------------+---------------+ | Set status | NoError | | NoError | NoError | | column | | | | | | to | | (9) | (7) | (7) | | Destroy | State = A | | State = A | State = A | +-------------+---------------+---------------+---------------+---------------+ | Get | NoSuchInstance| | NoError | NoError | | any column | (4) | (9) | (8) | (8) | | value | State = A | | State = C | State = D | +-------------+---------------+---------------+---------------+---------------+ (1) CreateAndGo is not supported in the IPDSLAM because the application receiving the command does not receive all parameters for the conceptual row in the table simultaneously but as a series of commands. (2) Temporary instance of the conceptual row is created for the Management, and placed in state NotInService. (3) If an instance of the conceptual row exists in Runtime, then copy it to the temporary instance. (4) The instance of the conceptual row does not exist in the Management and Runtime. (5) Data from the temporary instance of the conceptual row is copied to the runtime instance and the conceptual row is set to state Active. The temporary instance is deleted. (6) Temporary instance of the conceptual row is created for the Management, and placed in state NotInService. Data from the runtime instance of the conceptual row is copied to the temporary instance and the runtime instance is deleted. (7) The conceptual row may exist is two instances, a temporary management instance and a runtime instance. - Loop through all the connections and find for which connections ACL is being used - If the ACL is not used for any connection, then delete ACL (the management and runtime instance), otherwise return SnmpError. (8) If a temporary management instance of the row exists, then the read operation returns the variable value from that instance, otherwise the returned value is taken from the runtime instance. (9) The conceptual row will never exist in notReady state Valid from: EDA 2.2 SP2

This table is used to add/delete individual access rule statement in an EtherType Access Control List. The order of the rules is very important. The rules are processed in a top down order. Once a match is found, no further rules are processed. If no match is found, the packet is dropped. Valid from: EDA 2.2 SP2

An entry in the EtherType ACL Rule Table. Valid from: EDA 2.2 SP2

The Access Control List may have multiple rules. The ipAclRuleIndex specifies the position of the particular rule in the ACL. Valid from: EDA 2.2 SP2

Indicates the action to be taken when packet meets the filtering condition in an ACL Rule. permit: Every packet that matches rule condition is forwarded for further processing. deny: Every packet that matches rule condition is discarded. The value cannot be changed while the Rule is Active. Valid from: EDA 2.2 SP2 Enumeration: 'deny': 0, 'permit': 1.

This number indicates the Ethernet type to match to have a match on the rule. Zero means any Ethernet type will match the rule. A list of standardized Ethernet type numbers is maintained by IANA (Internet Assigned Numbers Authority). Valid from: EDA 2.2 SP2

This object is used to manage creation, deletion and modification of rows in the Access Control List Rule Table. Due to the way SNMP is handled in the IPDSLAM and the configuration file verification, RowStatus is handled slightly different in the IPDSLAM compared to the way described in RFC 2579. Below is a state/event table describing how the RowStatus will be handled in the IPDSLAM. The action to take and the return value assumes that the index to the table is valid. +-------------+---------------+---------------+---------------+---------------+ | Command | A | B | C | D | | | status column | status column | status column | status column | | |does not exist | notReady | notInService | is active | +-------------+---------------+---------------+---------------+---------------+ | Set status | Inconsistent | | Inconsistent | Inconsistent | | column | Value | | Value | Value | | to | (1) | (10) | (1) | (1) | | CreateAndGo | State = A | | State = C | State = D | +-------------+---------------+---------------+---------------+---------------+ | Set status | NoError | | NoError | NoError | | column to | (2) | (10) | (2) | (2)(3) | |CreateAndWait| State = C | | State = C | State = C | +-------------+---------------+---------------+---------------+---------------+ | Set status | Inconsistent | | NoError | NoError | | to | Value | | | | | | (4) | (10) | (5) | | | Active | State = A | | State = D | State = D | +-------------+---------------+---------------+---------------+---------------+ | Set status | Inconsistent | | NoError | NoError | | column | Value | | | | | to | (4) | (10) | | (6) | | NotInService| State = A | | State = C | State = C | +-------------+---------------+---------------+---------------+---------------+ | Set status | Inconsistent | Inconsistent | Inconsistent | Inconsistent | | column | Value | Value | Value | Value | | to | | | | | | NotReady | State = A | State = B | State = C | state = D | +-------------+---------------+---------------+---------------+---------------+ | Set status | NoError | | NoError | NoError | | column | | | | | | to | | (10) | (7) | (7) | | Destroy | State = A | | State = A | State = A | +-------------+---------------+---------------+---------------+---------------+ |Set any other| Inconsistent | | NoError | Inconsistent | |column to | Name | (10) | | Value | |some value | (4) | | | (8) | | | State = A | | State = C | State = D | +-------------+---------------+---------------+---------------+---------------+ | Get | NoSuchInstance| | NoError | NoError | | any column | (4) | (10) | (9) | (9) | | value | State = A | | State = C | State = D | +-------------+---------------+---------------+---------------+---------------+ (1) CreateAndGo is not supported in the IPDSLAM because the application receiving the command does not receive all parameters for the conceptual row in the table simultaneously but as a series of commands. (2) Temporary instance of the conceptual row is created for the management and placed in state NotInService. (3) If an instance of the conceptual row exists in runtime, it is copied to the temporary instance. (4) The instance of the conceptual row does not exists in management and runtime. (5) Data from the temporary instance of the conceptual row is copied to the runtime instance and the conceptual row is set to state Active. The temporary instance is deleted. (6) Temporary instance of the conceptual row is created in the management and placed in state NotInService. Data from the runtime instance of the conceptual row is copied to the temporary instance and the runtime instance is deleted. (7) The conceptual row may exist is two instances, a temporary management instance and a runtime instance. Both instances are deleted. (8) The ACL rule cannot be edited when conceptual row is Active. (9) If a temporary management instance of the row exists, then the read operation returns the variable value from that instance, otherwise the returned value is taken from the runtime instance. (10) The conceptual row can never exist in state notReady. Valid from: EDA 2.2 SP2

This table maintains a list of IP Access Control Lists in the IPDSLAM. Each Access Control List is made up of a group of access rules. The access rules are stored in the ipAclRuleTable. This table is used to add/delete IP Access Control Lists. ACL's are statements which are called rules of ACL that are grouped together by a number. Within this group of statements, when a packet is processed by an ACL on the IPDSLAM, the IPDSLAM will go through certain steps in finding a match against the ACL statements. ACL's are processed top-down by the IPDSLAM. Using a top-down approach, a packet is compared to the first statement in the ACL, and if the IPDSLAM finds a match between the packet and the statement, the IPDSLAM will execute one of two actions included with the statement: - Permit - Deny If the IPDSLAM doesn't find a match of packet contents to the first ACL statement, the IPDSLAM will proceed to the next statement in the list, again going through the same matching process If there isn't a match on this statement, the IPDSLAM will keep on going through the list until it finds a match. If the IPDSLAM goes through the entire list and doesn't find a match, the IPDSLAM will drop the packet. If there is a match on a statement, no further statements are processed. Therefore, the order of the statements is very important in an ACL. Valid from: EDA 2.2 SP2

An entry in the ipAclTable. Valid from: EDA 2.2 SP2

Index of the IP Access Control List. Valid from: EDA 2.2 SP2

Total number of rules in the IP Access Control List (ACL). Valid from: EDA 2.2 SP2

This object is used to manage the creation, deletion and modification of rows in the IP Access Control List Table. Due to the way SNMP is handled in the IPDSLAM and the configuration file verification, RowStatus is handled slightly different in the IPDSLAM compared to the way described in RFC 2579. Below is a state/event table describing how the RowStatus will be handled in the IPDSLAM. The action to take and the return value assumes that the index to the table is valid. +-------------+---------------+---------------+---------------+---------------+ | Command | A | B | C | D | | | status column | status column | status column | status column | | |does not exist | notReady | notInService | is active | +-------------+---------------+---------------+---------------+---------------+ | Set status | Inconsistent | | Inconsistent | Inconsistent | | column | Value | | Value | Value | | to | (1) | (9) | (1) | (1) | | CreateAndGo | State = A | | State = C | State = D | +-------------+---------------+---------------+---------------+---------------+ | Set status | NoError | | NoError | NoError | | column to | (2) | (9) | (2) | (2)(3) | |CreateAndWait| State = C | | State = C | State = C | +-------------+---------------+---------------+---------------+---------------+ | Set status | Inconsistent | | NoError | NoError | | to | Value | | | | | | (4) | (9) | (5) | | | Active | State = A | | State = D | State = D | +-------------+---------------+---------------+---------------+---------------+ | Set status | Inconsistent | | NoError | NoError | | column Value| | | | | | to | (4) | (9) | | (6) | | NotInService| State = A | | State = C | State = C | +-------------+---------------+---------------+---------------+---------------+ | Set status | Inconsistent | Inconsistent | Inconsistent | Inconsistent | | column | Value | Value | Value | Value | | to | | | | | | NotReady | State = A | State = B | State = C | state = D | +-------------+---------------+---------------+---------------+---------------+ | Set status | NoError | | NoError | NoError | | column | | | | | | to | | (9) | (7) | (7) | | Destroy | State = A | | State = A | State = A | +-------------+---------------+---------------+---------------+---------------+ | Get | NoSuchInstance| | NoError | NoError | | any column | (4) | (9) | (8) | (8) | | value | State = A | | State = C | State = D | +-------------+---------------+---------------+---------------+---------------+ (1) CreateAndGo is not supported in the IPDSLAM because the application receiving the command does not receive all parameters for the conceptual row in the table simultaneously but as a series of commands. (2) Temporary instance of the conceptual row is created for the Management, and placed in state NotInService. (3) If an instance of the conceptual row exists in Runtime, then copy it to the temporary instance. (4) The instance of the conceptual row does not exist in the Management and Runtime. (5) Data from the temporary instance of the conceptual row is copied to the runtime instance and the conceptual row is set to state Active. The temporary instance is deleted. (6) Temporary instance of the conceptual row is created for the Management, and placed in state NotInService. Data from the runtime instance of the conceptual row is copied to the temporary instance and the runtime instance is deleted. (7) The conceptual row may exist is two instances, a temporary management instance and a runtime instance. - Loop through all the connections and find for which connections ACL is being used - If the ACL is not used for any connection, then delete ACL (the management and runtime instance), otherwise return SnmpError. (8) If a temporary management instance of the row exists, then the read operation returns the variable value from that instance, otherwise the returned value is taken from the runtime instance. (9) The conceptual row will never exist in notReady state Valid from: EDA 2.2 SP2

This table is used to add/delete individual access rule statement in an IP Access Control List. The order of the rules is very important. The rules are processed in a top down order. Once a match is found, no further rules are processed. If no match is found, the packet is dropped. Valid from: EDA 2.2 SP2

An entry in the IP ACL Rule Table. Valid from: EDA 2.2 SP2

The Access Control List may have multiple rules. The ipAclRuleIndex specifies the position of the particular rule in the ACL. Valid from: EDA 2.2 SP2

Indicates the action to be taken when packet meets the filtering condition in an ACL Rule. permit: Every packet that matches rule condition is forwarded for further processing. deny: Every packet that matches rule condition is discarded. The value cannot be changed while the Rule is Active. Valid from: EDA 2.2 SP2 Enumeration: 'deny': 0, 'permit': 1.

ipAclIpProtocol identifies the layer above IP to which the IP packet data should be passed. The numbers associated with some important transport protocols are 1(icmp),2(igmp),6(tcp),17(udp). The value cannot be changed while the Rule is Active. The default value of -1 is used to match on any IP protocol. Valid from: EDA 2.2 SP2

The type of Internet address used in the ACL Rule. The ipAclIpAddrType will determine the value of ipAclSrcIpAddrMin, ipAclSrcIpAddrMax, ipAclDestIpAddrMin and ipAclDestIpAddrMax. The value cannot be changed while the Rule is Active. Currently the IPDSLAM only supports Ipv4. Valid from: EDA 2.2 SP2

ipAclSrcIpAddrMin is a 32-bit IP address (0.0.0.0 through 255.255.255.255), which defines the first element of the intended IP source address range. ipAclSrcIpAddrMin and ipAclSrcIpAddrMax together indicate a range of IP addresses of hosts. IP packets from hosts in that range will be filtered, depending on the value of the action field. The value cannot be changed while the Rule is Active. The default value is 0.0.0.0 . Valid from: EDA 2.2 SP2

ipAclSrcIpAddrMax is a 32-bit IP address (0.0.0.0 through 255.255.255.255), which defines the last element of the intended IP source address range. ipAclSrcIpAddrMin and ipAclSrcIpAddrMax together indicate a range of IP addresses of hosts. IP packets from hosts in that range will be filtered, depending on the value of the action field. The value cannot be changed while the Rule is Active. The default value is 255.255.255.255. Valid from: EDA 2.2 SP2

ipAclDestIpAddrMin is a 32-bit IP address (0.0.0.0 through 255.255.255.255), which defines the first element of the intended IP destination address range. ipAclDestIpAddrMin and ipAclDestIpAddrMax together indicate a range of IP addresses of hosts. IP packets to hosts in that range will be filtered, depending on the value of the action field. The value cannot be changed while the Rule is Active. The default value is 0.0.0.0. Valid from: EDA 2.2 SP2

ipAclDestIpAddrMax is a 32-bit IP address (0.0.0.0 through 255.255.255.255), which defines the last element of the intended IP destination address range. ipAclDestIpAddrMin and ipAclDestIpAddrMax together indicate a range of IP addresses of hosts. IP packets to hosts in that range will be filtered, depending on the value of the action field. The value cannot be changed while the Rule is Active. The default value is 255.255.255.255. Valid from: EDA 2.2 SP2

Indicates how a packet's source TCP/UDP port number is to be compared. noOperator(1) which is the default value, means that no comparison is to be made with the source TCP/UDP port number. lt(2) means less than, gt(3) means greater than, eq(4) means equal, neq(5) means not equal. These 4 operators will use srcPort object as an operand which is the only one needed. range(6) means that it compares the port value between two numbers, so this operator needs 2 operands. One operand is the starting port number of the range which is srcPort object, and the other operand is the ending port number of the range which is srcPortRange object. The value cannot be changed while the Rule is Active. Valid from: EDA 2.2 SP2 Enumeration: 'gt': 3, 'range': 6, 'noOperator': 1, 'lt': 2, 'eq': 4, 'neq': 5.

The source port number of the TCP or UDP protocol. If the ipAclSrcPortOp is set to range(6), this object will be the starting port number of the port range. The value cannot be changed while the Rule is Active. The default value for ipAclSrcPort is 0. Valid from: EDA 2.2 SP2

The source port number of the TCP or UDP protocol. If the ipAclSrcPortOp is set to range(6), this object will be the ending port number of the port range. The value cannot be changed while the Rule is Active. The default value for ipAclSrcPortRange is 65535. Valid from: EDA 2.2 SP2

Indicates how a packet's destination TCP/UDP port number is to be compared. noOperator(1) which is the default value, means that no comparison is to be made with the destination TCP/UDP port number. lt(2) means less than, gt(3) means greater than, eq(4) means equal, neq(5) means not equal. These 4 operators will use the destPort object as an operand which is the only one needed. range(6) means that it compares the port value between two numbers, so this operator needs 2 operands. One operand is the starting port number of the range which is destPort object, and the other operand is the ending port number of the range which is destPortRange object. The value cannot be changed while the Rule is Active. Valid from: EDA 2.2 SP2 Enumeration: 'gt': 3, 'range': 6, 'noOperator': 1, 'lt': 2, 'eq': 4, 'neq': 5.

The destination port number of the TCP or UDP protocol. If the ipAclDestPortOp is set to range(6), this object will be the starting port number of the port range. The value cannot be changed while the Rule is Active. The default value for ipAclDestPort is 0. Valid from: EDA 2.2 SP2

The destination port number of the TCP or UDP protocol. If the ipAclDestPortOp is set to range(6), this object will be the ending port number of the port range. The value cannot be changed while the Rule is Active. The default value for ipAclDestPortRange is 65535. Valid from: EDA 2.2 SP2

Value of the TCP Control code/flags. The parameter specifies if a flag must be set or cleared to have a match. ---------------------------------- |MSB| | | | | | | LSB | | x | x | U | A | P | R | S | F | ---------------------------------- The various bit positions are: 1 - F,FIN End of data flag. 2 - S,SYN Synchronize sequence numbers flag. 3 - R,RST Reset connection flag. 4 - P,PSH Push flag. 5 - A,ACK Acknowledgment number valid flag. 6 - U,URG Urgent pointer valid flag. For Example: To test on SYN flag set and ACK flag cleared, value should be xxx1xx0x where x is don't care and can be set to either 0 or 1. ipAclTcpFlagsMask specified for which of the flags the test is carried out. The ipAclTcpFlags is used in combination with ipAclTcpFlagsMask and ipAclTcpFlagsMatchMethod. The value cannot be changed while the Rule is Active. Valid from: EDA 2.2 SP2

Value of the TCP Control code/flags mask. The ipAclTcpFlagsMask specifies which of the TCP Control flags specified in tcpFlags to match. ---------------------------------- |MSB| | | | | | | LSB | | 0 | 0 | U | A | P | R | S | F | ---------------------------------- The various bit positions are: 1 - F,FIN End of data flag. 2 - S,SYN Synchronize sequence numbers flag. 3 - R,RST Reset connection flag. 4 - P,PSH Push flag. 5 - A,ACK Acknowledgment number valid flag. 6 - U,URG Urgent pointer valid flag. For Example: To match on SYN and ACK flag, value should be 00010010, then the test will only be performed for SYN and ACK. Whether the flags must be set or cleared to have a match is specified in ipAclTcpFlags. The ipAclTcpFlagsMask is used in combination with ipAclTcpFlags and ipAclTcpFlagsMatchMethod. The value cannot be changed while the Rule is Active. Valid from: EDA 2.2 SP2

The ipAclTcpFlagsMatchMethod specified whether all (matchAll) or just one or more (matchAny) TCP flags must be correct to have a match in the TCP flags part of the rule. The ipAclTcpFlagsMatchMethod is used in combination with ipAclTcpFlags and ipAclTcpFlagsMask. The value cannot be changed while the Rule is Active. Valid from: EDA 2.2 SP2 Enumeration: 'matchAll': 1, 'matchAny': 0.

Value of ICMP type. ICMP type defines the ICMP message that is being passed. The default value of -1 for ipAclIcmpType is used to match on all the ICMP Types. The value cannot be changed while the Rule is Active. Valid from: EDA 2.2 SP2

Value of ICMP code. In certain cases, an ICMP type may have several submessages. A submessage is called an ICMP code. When an ICMP message requires only a type, the ICMP code will be set to 0. The default value of -1 for ipAclIcmpCode is used to match on all ICMP Codes. The value cannot be changed while the Rule is Active. Valid from: EDA 2.2 SP2

Value of IGMP type. IGMP type defines the IGMP message that is being passed.The default value of -1 for ipAclIgmpType is used to match on all the IGMP Types. The value cannot be changed while the Rule is Active. Valid from: EDA 2.2 SP2

This object is used to manage creation, deletion and modification of rows in the Access Control List Rule Table. Due to the way SNMP is handled in the IPDSLAM and the configuration file verification, RowStatus is handled slightly different in the IPDSLAM compared to the way described in RFC 2579. Below is a state/event table describing how the RowStatus will be handled in the IPDSLAM. The action to take and the return value assumes that the index to the table is valid. +-------------+---------------+---------------+---------------+---------------+ | Command | A | B | C | D | | | status column | status column | status column | status column | | |does not exist | notReady | notInService | is active | +-------------+---------------+---------------+---------------+---------------+ | Set status | Inconsistent | | Inconsistent | Inconsistent | | column | Value | | Value | Value | | to | (1) | (10) | (1) | (1) | | CreateAndGo | State = A | | State = C | State = D | +-------------+---------------+---------------+---------------+---------------+ | Set status | NoError | | NoError | NoError | | column to | (2) | (10) | (2) | (2)(3) | |CreateAndWait| State = C | | State = C | State = C | +-------------+---------------+---------------+---------------+---------------+ | Set status | Inconsistent | | NoError | NoError | | to | Value | | | | | | (4) | (10) | (5) | | | Active | State = A | | State = D | State = D | +-------------+---------------+---------------+---------------+---------------+ | Set status | Inconsistent | | NoError | NoError | | column | Value | | | | | to | (4) | (10) | | (6) | | NotInService| State = A | | State = C | State = C | +-------------+---------------+---------------+---------------+---------------+ | Set status | Inconsistent | Inconsistent | Inconsistent | Inconsistent | | column | Value | Value | Value | Value | | to | | | | | | NotReady | State = A | State = B | State = C | state = D | +-------------+---------------+---------------+---------------+---------------+ | Set status | NoError | | NoError | NoError | | column | | | | | | to | | (10) | (7) | (7) | | Destroy | State = A | | State = A | State = A | +-------------+---------------+---------------+---------------+---------------+ |Set any other| Inconsistent | | NoError | Inconsistent | |column to | Name | (10) | | Value | |some value | (4) | | | (8) | | | State = A | | State = C | State = D | +-------------+---------------+---------------+---------------+---------------+ | Get | NoSuchInstance| | NoError | NoError | | any column | (4) | (10) | (9) | (9) | | value | State = A | | State = C | State = D | +-------------+---------------+---------------+---------------+---------------+ (1) CreateAndGo is not supported in the IPDSLAM because the application receiving the command does not receive all parameters for the conceptual row in the table simultaneously but as a series of commands. (2) Temporary instance of the conceptual row is created for the management and placed in state NotInService. (3) If an instance of the conceptual row exists in runtime, it is copied to the temporary instance. (4) The instance of the conceptual row does not exists in management and runtime. (5) Data from the temporary instance of the conceptual row is copied to the runtime instance and the conceptual row is set to state Active. The temporary instance is deleted. (6) Temporary instance of the conceptual row is created in the management and placed in state NotInService. Data from the runtime instance of the conceptual row is copied to the temporary instance and the runtime instance is deleted. (7) The conceptual row may exist is two instances, a temporary management instance and a runtime instance. Both instances are deleted. (8) The ACL rule cannot be edited when conceptual row is Active. (9) If a temporary management instance of the row exists, then the read operation returns the variable value from that instance, otherwise the returned value is taken from the runtime instance. (10) The conceptual row can never exist in state notReady. Valid from: EDA 2.2 SP2

A list of entries to the subscriber IP filter type list.

The lineIndex and pvcIndex pair forms a unique identification of a PVC in the managed device. A subsIpFilterTypeEntry contains subscriber IP filter type information for a PVC.

Specifies whether the subscriber IP filter is positive or disabled. If the filter is positive, the managed device is allowed to forward traffic from/to subscribers if their IP address is specified in the subsIpFilterTable. If the subscriber IP filter is disabled, the managed device will make no filtering on subscriber IP. Whether the subscriber IP filter is positive or disabled is specified per PVC. Valid from: EDA 2.2 R3A Enumeration: 'disabled': 2, 'positive': 0.

A list of entries to the subscriber IP filter list.

The lineIndex and pvcIndex pair forms a unique identification of a PVC in the managed device. A subsIpFilterEntry contains subscriber IP filter information for a PVC. Each entry describes a range of consecutive subscriber IP addresses which are allowed to forward traffic on the PVC. If the subscriber IP filter is empty, no traffic is allowed, F.ex. if subscriber Internet addresses in the range 10.0.0.1 to 10.0.0.254 are allowed on the PVC, a positive (0) subscriber IP filter should be used, subsIpFilterFirstAddress is set to 10.0.0.1 and subsIpFilterLastAddress is set to 10.0.0.254. Multiple entries may be required to describe the complete subscriber IP filter for one PVC. Valid from: EDA 2.2 R3A

The type of Internet address used in the subscriber IP filter address range. Valid from: EDA 2.2 R3A

The first address in the subscriber Internet address range. The type of this address is determined by the value of the subsIpFilterAddressType object. The subsIpFilterFirstAddress may not be empty due to the SIZE restriction. Valid from: EDA 2.2 R3A

The last address in the subscriber Internet address range. The type of this address is determined by the value of the subsIpFilterAddressType object. subsIpFilterLastAddress must be a equal to or higher than subsIpFilterFirstAddress before the settings are put into operation. The subsIpFilterLastAddress may not be empty due to the SIZE restriction. To modify the value of subsIpFilterLastAddress, the conceptual row must be taken Out of Service Valid from: EDA 2.2 R3A

The subsIpFilterRowStatus is used to manage the creation and deletion of rows in subsIpFilterTable. Valid from: EDA 2.2 R3A

priorityIndex is used to access a number of tables regarding Weighted Random Early Discard (WRED). Those tables are indexed per line, PVC and VLAN priority index. The relation between priorityIndex and VLAN priority is: priorityIndex = VLAN priority + 1. Valid from: EDA 2.2 R3A

The IP-DSLAM flow implementation allows multiple VLAN priorities to be mapped to the same downstream flow queue (downstream flows are configured with downstreamFlowConfigTable). Parameters in the downstreamFlowWredConfigTable are used to configure the discard probability of packets with different VLAN priority in the same downstream flow. The mechanisms Weighted Random Early Discard (WRED) is implemented to allow configuration of discard probability of packet with different VLAN priority. The WRED mechanism works as an extention to the other flow mechanisms in the IP-DSLAM. IP DSLAM __________________________________________________________________ | ______ | | ( ) ___ _ _ _ _ | | /--->( WRED )--->___Q3_|_|_|_|-->\ | | / (______) \ | | / ______ \ | | / ( ) ___ _ _ _ _ \ | | ___________/___/--->( WRED )--->___Q2_|_|_|_|-->\___\_______ | Aggregation | ( VLAN priority ) (______) ( ) | Network ---->|->( to flow ) ______ ( Scheduler )->|--> End-user | (____mapping____) ( ) ___ _ _ _ _ (___________) | | \ \--->( WRED )--->___Q1_|_|_|_|-->/ / | | \ (______) / | | \ ______ / | | \ ( ) ___ _ _ _ _ / | | \--->( WRED )--->___Q0_|_|_|_|-->/ | | (______) | | | | WRED = Weighted Random Early Discard | |__________________________________________________________________| The figure above illustrates where in the flow handling process the WRED is performed. Weighted Random Early Discard (WRED) is needed to ensure that high priority packets are favored over low priority packets when the downstream flow queue buffer usage gets close to the maximum buffer limit. Maximum buffer limit is configured with dfcMaxQueueBuffers. A flow has one downstream flow queue associated. All packets for this flow will be stored in the downstream flow queue, disregarding the packets VLAN priority, until they in turn are forwarded to the PVC in the subscriber line. The parameters wredBufferLimit and wredDropProbability are used to configure the WRED mechanism. dfcMaxQueueBuffers | V____________________________________________________________________________________ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Downstream flow queue | | | | | | | | | | | | |_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|________________________________|_|_|_|_|_|_|_|_|_|_|_| ^ ^ V | | | wredBufferLimit(x) wredBufferLimit(y) dfcMaxQueueBuffers (100%) (70%) in steps of 1 buffer In the figure above is illustrated that packets with VLAN priority X will not be discarded until all buffers in the downstream flow queue are in use while the WRED mechanism will start discarding packets with VLAN priority Y when 70% of the buffers in the downstream flow queue are in use. Valid from: EDA 2.2 R3A

This is an entry in the downstreamFlowWredConfigTable and contains the parameters to configure the WRED mechanism for one VLAN priority in the downstream flows for one end-user connection. Valid from: EDA 2.2 R3A

Weighted Random Early Discard (WRED) buffer limit specifies the queue usages limit for traffic with a specific VLAN priority. The drop limit is specified as a percentage of the total queue length (dfcMaxQueueBuffers) for the Flow. F.ex. if the flow queue can contain 100 packets and wredBufferLimit is set to 70%, then the IP-DSLAM WRED mechanism will start dropping packets with the specific VLAN priority when more than 70 buffers from the queue is in use. Valid from: EDA 2.2 R3A

wredDropProbability is used to specify the probability that a packet with a specific VLAN priority will be dropped if the wredBufferLimit has been exceeded. wredDropProbability is configured as a percentage of all packets received with the VLAN priority, e.g. if 80% drop probability has been specified, 4 out of 5 packets with this VLAN priority will be dropped when wredBufferLimit has been exceeded. If wredBufferLimit is set to 100% wredDropProbability has no effect. Valid from: EDA 2.2 R3A

The downstreamFlowWredStatisticsTable contains statistics counters for the Weighted Random Early Discard (WRED) mechanism. Valid from: EDA 2.2 R3A

The downstreamFlowWredStatisticsEntry contains Weighted Random Early Discard (WRED) statistics for one VLAN priority in a downstream flow. Valid from: EDA 2.2 R3A

The number of packets that have passed the Weighted Random Early Discard (WRED) mechanism. Valid from: EDA 2.2 R3A

The number of packets that have been discarded by the Weighted Random Early Discard (WRED) mechanism. Valid from: EDA 2.2 R3A

The number of bytes that have passed the Weighted Random Early Discard (WRED) mechanism. Valid from: EDA 2.2 R3A

The number of bytes that have been discarded by the Weighted Random Early Discard (WRED) mechanism. Valid from: EDA 2.2 R3A

This table contains a list of subscriber information that the IP-DSLAM has dynamically learned. From the list it is possible to get the relationship between subscriber MAC and IP addresses. When running DHCP it is also possible to readout the IP-DSLAM equivalent of the LeaseTime. This is the time where the IP-DSLAM will remove the IP address and MAC address from the filters. The learned gateway IP and MAC can also be readout from the IP-DSLAM. The table is indexed by lineIndex, pvcIndex, subscriberInfoMac and subscriberInfoIp. Valid from: EDA 2.2 R3A

An entry containing the subscriber information identified by lineIndex, pvcIndex, subscriberInfoMac and subscriberInfoIp address. Valid from: EDA 2.2 R3A

The MAC address of the subscriber which is learned by the IP-DSLAM. Valid from: EDA 2.2 R3A

For StaticIP, DHCP and DHCPIP over ATM access methods, relationship between MAC address of the subscriber and IP address of the subscriber is maintained in the IP-DSLAM. For these three access methods, subscriberInfoIp will contain the IP address of the subscriber. For other access methods, the subscriberInfoIp will contain 0.0.0.0 value. Valid from: EDA 2.2 R3A

subscriberInfoVirtualMac will contain the virtual MAC address of the subscriber generated by the IP-DSLAM only when - peaBridgeIpDslam::virtualMacEnable is set to true for the PVC and - peaBridgeIpDslam::accessMethod is other than Transparent LAN, StaticIP over ATM or PPP over ATM. subscriberInfoVirtualMac will contain 00:00:00:00:00:00 value when - peaBridgeIpDslam::virtualMacEnable is set to false for the PVC or - peaBridgeIpDslam::accessMethod is Transparent LAN, StaticIP over ATM or PPP over ATM. Valid from: EDA 2.2 R3A

The IP address lease time for the subscriber when DHCP is used as access method. For other access methods the DateAndTime string will be read out as empty. The lease time read out from IP-DSLAM will be the GMT time. The DateAndTime format: field octets contents range ----- ------ -------- ----- 1 1-2 year 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC 0..11 10 11 minutes from UTC 0..59 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Valid from: EDA 2.2 R3A

If True the Ethernet frames originated from the subscriber will be forwarded to a gateway. The value can be either True(1) or False(2). Valid from: EDA 2.2 R3A

The IP address of the gateway used by the subscriber. The subscriberInfoGatewayIp will contain 0.0.0.0 value when peaBridgeIpDslam::gatewayIp is not set for the PVC or gateway IP address is not learned in case of DHCP or DHCPIP over ATM access methods. Valid from: EDA 2.2 R3A

The MAC address of the gateway used by the subscriber which is learned by the IP-DSLAM. The subscriberInfoGatewayMac will contain 00:00:00:00:00:00 value when - peaBridgeIpDslam::gatewayIp is not set for the PVC or gatewayIp is not learned in case of DHCP or DHCPIP over ATM access methods. - peaBridgeIpDslam::gatewayFixedForwarding is set to false for the PVC. - IP-DSLAM is unable to resolve the peaBridgeIpDslam::gatewayIp. Valid from: EDA 2.2 R3A

Table containing the IGMP membership information for each Multicast Group Address learned by IGMP Snooping. With IGMP Snooping enabled,the IP DSLAM can 'listen in' on the IGMP conversation between IP Multicast Hosts and Routers, to learn the group memberships. When it hears an IGMP Join/Report from a host for a given multicast group, the IP DSLAM adds the host's MAC address to the Source MAC Address List for that group. And, when the IP DSLAM hears an IGMP Leave, it removes the host's MAC address entry. Thus multicast traffic of a group is forwarded only to the members of that group, thereby reducing the network traffic.

A mcastGroupInfoEntry is created for each multicast group learned on a PVC, when any subscriber joins the multicast group. For an mcastGroupInfoEntry created by any IGMP Msg from Network, the lineIndex is 0 and the pvcIndex is 0.

This object indicates the VLAN in which the multicast group is learned.

This object indicates the IP address of the multicast group learned.

This object indicates the MAC address of the host which is a member of the Muticast Group.

IGMP Version 3 (IGMPv3) adds support for 'source filtering', which enables a multicast receiver host to explicitly signal sources from which they want to receive traffic. mcastGroupSourceFilterIPAddress is specified in the IGMPv3 Membership Reports and indicates the source address from which traffic is expected. Groups for which IGMPv1/v2 Membership Reports are received are considered to have a mcastGroupSourceFilterIPAddress of 0.0.0.0

This object indicates the type of IGMP messages that are transmitted and received for the Multicast Group. The values for different IGMP message types are : IGMP Message Type Value ----------------- ------ IGMP_QUERY 0x0001 IGMPv1_REPORT 0x0002 IGMPv2_REPORT 0x0004

This object indicates the time elapsed since the mcastGroupIgmpMsgType was first received/transmitted.

The value of nodeId uniquely identifies the traffic statistics of the IPDSLAM. The default value for IPDSLAM is always one. Valid from: EDA 2.2 SP3

This table contains list of upstream and downstream traffic statistics entries of IPDSLAM. Valid from: EDA 2.2 SP3

An entry is a collection of upstream and downstream traffic statistics kept for the IPDSLAM. Valid from: EDA 2.2 SP3

Total number of Ethernet packets received from the network. Valid from: EDA 2.2 SP3

Total number of untagged management packets received from the network. Valid from: EDA 2.2 SP3

Total number of tagged management packets received from the network. Valid from: EDA 2.2 SP3

Total number of non-management DHCP packets received from the network. Valid from: EDA 2.2 SP3

Total number of PPP discovery packets received from the network. Valid from: EDA 2.2 SP3

Total number of non-management broadcast packets received from the network. Valid from: EDA 2.2 SP3

Total number of non-management ARP packets received from the network. Valid from: EDA 2.2 SP3

Total number of L2CP packets received from the network. Valid from: EDA 2.2 SP3

Total number of Ethernet packets from the network flooded to the subscribers in the same VLAN due to destination MAC address unknown in IPDSLAM. Valid from: EDA 2.2 SP3

Total number of packets received from the subscribers. Valid from: EDA 2.2 SP3

Total number of DHCP packets received from the subscribers. Valid from: EDA 2.2 SP3

Total number of PPP discovery packets received from the subscribers. Valid from: EDA 2.2 SP3

Total number of ARP packets received from the subscribers. Valid from: EDA 2.2 SP3

Total number of Ethernet packets received from the subscriber and sent to other subscribers connected on the same IPDSLAM. Valid from: EDA 2.2 SP3

This parameter resets all the trafStatNodeMain traffic statistics of the IPDSLAM to zero. Valid from: EDA 2.2 SP3 Enumeration: 'clear': 1.

This table contains list of upstream and downstream multicast traffic statistics entries of IPDSLAM. Valid from: EDA 2.2 SP3

An entry is a collection of upstream and downstream multicast traffic statistics kept for the IPDSLAM. Valid from: EDA 2.2 SP3

Total number of IP multicast packets received from the network. Valid from: EDA 2.2 SP3

Total number of multicast control (Non-UDP) packets received from the network. Valid from: EDA 2.2 SP3

Total number of IP multicast packets received from the subscribers. Valid from: EDA 2.2 SP3

Total number of multicast control (Non-UDP) packets received from the subscribers. Valid from: EDA 2.2 SP3

Total number of multicast packets received which gets flooded to the network and subscribers in same VLAN. Valid from: EDA 2.2 SP3

Total number of IGMP Groups which have atleast one active member. IGMP Group is identified by the multicast group address and vlan. e.g 1) If IGMP Group [G1,V1] and [G1,V2] have atleast one active member, then tsnNoOfIgmpGroups will be two. 2) If IGMP Group [G1,V1],[G2,V1] and [G3,V2] have atleast one active member, then tsnNoOfIgmpGroups will be three. Valid from: EDA 2.2 SP3

Total number of IGMP entries for which there is - Atleast one active member. - Atleast one active querier. IGMP entry is identified by PVC, multicast group address and vlan. Valid from: EDA 2.2 SP3

Total number of IGMP Query packets received either from network or subscribers. Valid from: EDA 2.2 SP3

Total number of IGMP Report packets received either from network or subscribers. Valid from: EDA 2.2 SP3

Total number of IGMP Leave packets received either from network or subscribers. Valid from: EDA 2.2 SP3

This parameter resets all the trafStatNodeMcastMain traffic statistics of the IPDSLAM to zero. Valid from: EDA 2.2 SP3 Enumeration: 'clear': 1.

This table contains list of upstream and downstream error traffic statistics of the IPDSLAM. Valid from: EDA 2.2 SP3

An entry is a collection of upstream and downstream error traffic statistics kept for the IPDSLAM. Valid from: EDA 2.2 SP3

Total number of non-multicast Ethernet packets from the network discarded by IPDSLAM. tsnDsTotalDiscardPkts = SUM[tsnDsUnknownDstPkts, tsnDsGatewayErrPkts, tsnDsVlanIdAclErrPkts, tsnDsEthTypeAclErrPkts, tsnDsIpAclFilterErrPkts] Valid from: EDA 2.2 SP3

Total number of Ethernet packets received from the network with unknown destination MAC address. Valid from: EDA 2.2 SP3

Total number of Ethernet packets received from the network and discarded due to : - gateway MAC address not resolved by the IPDSLAM - Source MAC address in the packet is not the gateway MAC address Valid from: EDA 2.2 SP3

Total number of Ethernet packets received from the network and discarded due to VLAN Id Access Control List filtering. Valid from: EDA 2.2 SP3

Total number of Ethernet packets received from the network and discarded due to Ethernet type Access Control List filtering. Valid from: EDA 2.2 SP3

Total number of IP packets received from the network and discarded due to IP Access Control List filtering. Valid from: EDA 2.2 SP3

Total number of non-multicast Ethernet packets from the subscribers discarded by IPDSLAM. tsnUsTotalDiscardPkts = SUM[tsnUsVlanIdAclErrPkts, tsnUsEthTypeAclErrPkts, tsnUsIpAclFilterErrPkts, tsnUsSrcMacErrPkts, tsnUsSrcIpErrPkts, tsnUsBcastErrPkts, tsnUsVmacErrPkts, tsnUsGatewayErrPkts, tsnUsSendErrPkts,tsnUsVlanTypeFltrErrPkts] Valid from: EDA 2.2 SP3

Total number of Ethernet packets received from the subscribers and discarded due to VLAN Id Access Control List filtering. Valid from: EDA 2.2 SP3

Total number of Ethernet packets received from the subscribers and discarded due to Ethernet type Access Control List filtering. Valid from: EDA 2.2 SP3

Total number of IP packets received from the subscribers and discarded due to IP Access Control List filtering. Valid from: EDA 2.2 SP3

Total number of Ethernet packets received from the subscribers and discarded due to : - source MAC not present in the subscriber MAC filter. - MAC limit exceeded on the PVC. Valid from: EDA 2.2 SP3

Total number of IP packets received from the subscribers and discarded due to source IP address filtering. Valid from: EDA 2.2 SP3

Total number of Ethernet packets received from the subscribers and discarded due to subscriber not allowed to send and receive Broadcast. Valid from: EDA 2.2 SP3

Total number of packets received from the subscribers and discarded due to maximum limit reached for number of virtual MAC addresses. Valid from: EDA 2.2 SP3

Total number of Ethernet packets received from the subscribers and discarded due to : - gateway MAC address not resolved by the IPDSLAM - Destination MAC address in the packet is not the gateway MAC address Valid from: EDA 2.2 SP3

Total number of non-multicast Ethernet packets received from the subscribers and discarded due to : - upstream policing - packet size exceeding peaBridgeIpDslam::maximumEthernetFrameSize Valid from: EDA 2.2 SP3

Total number of Ethernet packets received from the subscribers and discarded due to VLAN type filtering. Valid from: EDA 2.2 SP3

This parameter resets all the trafStatNodeErrors traffic statistics of the IPDSLAM to zero. Valid from: EDA 2.2 SP3 Enumeration: 'clear': 1.

This table contains list of upstream and downstream multicast error traffic statistics of the IPDSLAM. Valid from: EDA 2.2 SP3

An entry is a collection of upstream and downstream multicast error traffic statistics kept for the IPDSLAM. Valid from: EDA 2.2 SP3

Total number of multicast packets received from the network and discarded due to : - Non-IP multicast packet - Non-L2CP multicast packet Valid from: EDA 2.2 SP3

Total number of multicast UDP packets received from network and discarded due to unknown destination multicast group address. Valid from: EDA 2.2 SP3

Total number of multicast non-UDP packets received from network and discarded due to IP Access Control List filtering. Valid from: EDA 2.2 SP3

Total number of multicast packets received from network and discarded due to following errors in sending the packets to the susbcribers : - Illegal P-bit - Downstream policing - Vlan type filtering - Vlan Id Access Control List filtering - ATM layer not running. Valid from: EDA 2.2 SP3

Total number of multicast packets received from the subscribers and discarded due to : - Non-IP multicast packet - Non-L2CP multicast packet Valid from: EDA 2.2 SP3

Total number of multicast UDP packets received from the subscribers and discarded due to unknown destination multicast group address. Valid from: EDA 2.2 SP3

Total number of multicast packets received from the susbcribers and discarded due to : - IGMP snooping disabled on the PVC. - Upstream multicast disabled on the PVC. Valid from: EDA 2.2 SP3

Total number of multicast non-UDP packets received from the subscribers and discarded due to IP Access Control List filtering. Valid from: EDA 2.2 SP3

Total number of multicast packets received from the subscribers and discarded due to following errors in sending the packets to network. - upstream policing - packet size exceeding peaBridgeIpDslam::maximumEthernetFrameSize Valid from: EDA 2.2 SP3

Total number of IGMP packets discarded due to packet size less than minimum IGMP packet length (Ethernet + IP + IGMP header). Valid from: EDA 2.2 SP3

Total number of IGMP packets discarded due to unknown IGMP type in the IGMP header. Valid from: EDA 2.2 SP3

Total number of muticast packets received from the subscribers and discarded due to ADSL line being down. Valid from: EDA 2.2 SP3

Total number of IGMP Report packets discarded due to : - IGMP Report received from the network and upstream multicast not enabled for any subscriber in same Vlan. - Multicast group address not allowed for the subscriber by the multicast filter. - Multicast group limit (peaBridgeIpDslam::multicastGroupsLimit) exceeded for the subscriber. Valid from: EDA 2.2 SP3

Total number of IGMP Leave packets discarded due to : - Multicast group address not allowed for the subscriber by the multicast filter. Valid from: EDA 2.2 SP3

This parameter resets all the trafStatNodeMcastErrors traffic statistics of the IPDSLAM to zero. Valid from: EDA 2.2 SP3 Enumeration: 'clear': 1.

This table contains tsnClearStat parameter which resets the upstream and downstream traffic statistics of the IPDSLAM to zero. Valid from: EDA 2.2 SP3

An entry in the trafStatNodeClearTable. Valid from: EDA 2.2 SP3

This parameter resets all the following traffic statistics of the IPDSLAM to zero. - peaBridgeIpDslam::trafStatNodeMain - peaBridgeIpDslam::trafStatNodeMcastMain - peaBridgeIpDslam::trafStatNodeErrors - peaBridgeIpDslam::trafStatNodeMcastErrors Valid from: EDA 2.2 SP3 Enumeration: 'clear': 1.

This table contains list of upstream and downstream traffic statistics of the IPDSLAM for a specific PVC. Valid from: EDA 2.2 SP3

An entry is a collection of upstream and downstream traffic statistics kept for the IPDSLAM for a specific PVC. Valid from: EDA 2.2 SP3

Total number of Ethernet packets received from network and sent to the subscriber on the specified PVC. This parameter is an alias to pvcTable.downstreamFrameCount. Valid from: EDA 2.2 SP3

Total number of bytes received from network and sent to the subscriber on the specified PVC. This parameter is an alias to pvcTable.downstreamByteCount. Valid from: EDA 2.2 SP3

Total number of Ethernet packets per second received from network and sent to the subscriber on the specified PVC. This parameter is an alias to pvcTable.downstreamFramesPerSecond. Valid from: EDA 2.2 SP3

Total number of bits per second received from network and sent to the subscriber on the specified PVC. This parameter is an alias to pvcTable.downstreamBitsPerSecond. Valid from: EDA 2.2 SP3

Total number of unicast packets received from the network and sent to the subscriber on the specified PVC. Valid from: EDA 2.2 SP3

Total numbers of broadcast packets received from the network and sent to the subscriber on the specified PVC. Valid from: EDA 2.2 SP3

Total numbers of packets received from a subscriber connected on the same IPDSLAM and sent to subscriber on the specified PVC. Valid from: EDA 2.2 SP3

Total number of ARP packets received from network and sent to the subscriber on the specified PVC. Valid from: EDA 2.2 SP3

Total number of DHCP packets received from network and sent to the subscriber on the specified PVC Valid from: EDA 2.2 SP3

Total number of PPP discovery packets received from network and sent to the subscriber on the specified PVC. Valid from: EDA 2.2 SP3

Total number of L2CP tunneling packets received from network and sent to the subscriber on the specified PVC. Valid from: EDA 2.2 SP3

Total number of Ethernet packets received from the subscriber on the specified PVC and sent to the network. This parameter is an alias to pvcTable.upstreamFrameCount. Valid from: EDA 2.2 SP3

Total number of bytes received from the subscriber on the specified PVC and sent to network. This parameter is an alias to pvcTable.upstreamByteCount. Valid from: EDA 2.2 SP3

Total number of Ethernet packets per second received from the subscriber on the specified PVC and sent to the network. This parameter is an alias to pvcTable.upstreamFramesPerSecond. Valid from: EDA 2.2 SP3

Total number of bits per second received from the subscriber on the specified PVC and sent to network. This parameter is an alias to pvcTable.upstreamBitsPerSecond. Valid from: EDA 2.2 SP3

Total number of unicast packets received from the subscriber on the specified PVC and sent to network. Valid from: EDA 2.2 SP3

Total number of broadcast packets received from the subscriber on the specified PVC and sent to network. Valid from: EDA 2.2 SP3

Total numbers of packets received from the subscriber on the specified PVC and sent to another subscriber connected on same IPDSLAM. Valid from: EDA 2.2 SP3

Total number of ARP packets received from the subscriber on the specified PVC and sent to network. Valid from: EDA 2.2 SP3

Total number of DHCP packets received from the subscriber on the specified PVC and sent to network. Valid from: EDA 2.2 SP3

Total number of PPP discovery packets received from the subscriber on the specified PVC and sent to network. Valid from: EDA 2.2 SP3

Total number of L2CP tunneling packets received from the subscriber on the specified PVC and sent to network. Valid from: EDA 2.2 SP3

This parameter resets all the trafStatLogiPortMain traffic statistics of the IPDSLAM to zero. Valid from: EDA 2.2 SP3 Enumeration: 'clear': 1.

This table contains list of upstream and downstream error traffic statistics of the IPDSLAM for a specific PVC. Valid from: EDA 2.2 SP3

An entry is a collection of upstream and downstream error traffic statistics kept for the IPDSLAM for a specific PVC. Valid from: EDA 2.2 SP3

Total number of Ethernet packets received from the network and discarded for the specified PVC due to VLAN Id Access Control List filtering. Valid from: EDA 2.2 SP3

Total number of Ethernet packets received from the network and discarded for the specified PVC due to Ethernet type Access Control List filtering. Valid from: EDA 2.2 SP3

Total number of IP packets received from the network and discarded for the specified PVC due to IP Access Control List filtering. Valid from: EDA 2.2 SP3

Total number of Ethernet packets received from the network and discarded for the specified PVC due to - gateway MAC address not resolved by IPDSLAM - Source MAC address in the packet is not the gateway MAC address. Valid from: EDA 2.2 SP3

Total number of packets received from the network and discarded for the specified PVC due to : - destination MAC address not present in the subscriber MAC filter - MAC limit exceeded on the PVC Valid from: EDA 2.2 SP3

Total number of broadcast packets received from the network and discarded for the specified PVC due to : - Gateway MAC address not resolved by IPDSLAM. - Broadcast is not allowed on the specified PVC. Valid from: EDA 2.2 SP3

Total number of L2CP packets received by the subscriber on the specified PVC and discarded due to L2CP Tunneling not enabled for the received protocol. Valid from: EDA 2.2 SP3

Total number of Ethernet packets received from the subscriber on the specified PVC and discarded due to VLAN Id Access Control List filtering. Valid from: EDA 2.2 SP3

Total number of Ethernet packets received from the subscriber on the specified PVC and discarded due to Ethernet type Access Control List filtering. Valid from: EDA 2.2 SP3

Total number of IP packets received from the subscriber on the specified PVC and discarded due to IP Access Control List filtering. Valid from: EDA 2.2 SP3

Total number of Ethernet packets received from the subscribers on the specified PVC and discarded due to : - source MAC not present in the subscriber MAC filter - MAC limit exceeded on the PVC Valid from: EDA 2.2 SP3

Total number of IP packets received from the subscriber on the specified PVC and discarded due to source IP address in the packet not present in the subscriber IP filter. Valid from: EDA 2.2 SP3

Total number of Ethernet packets received from the subscriber on the specified PVC and discarded due to : - gateway MAC address not resolved by IPDSLAM - Destination MAC address in the packet is not the gateway MAC address Valid from: EDA 2.2 SP3

Total number of broadcast packets received from the subscriber on the specified PVC and discarded due to subscriber not allowed to send broadcast. Valid from: EDA 2.2 SP3

Total number of L2CP packets received from the subscriber on the specified PVC and discarded due to : - L2CP Tunneling not enabled for the received protocol. - Unsupported protocol by L2CP Tunnneling. Valid from: EDA 2.2 SP3

Total number of ICMP packets received from the subscriber on the specified PVC and discarded due to ICMP security filtering. Valid from: EDA 2.2 SP3

Total number of Ethernet packets received from the subscriber on the specified PVC and discarded due to packet size exceeding peaBridgeIpDslam::maximumEthernetFrameSize. Valid from: EDA 2.2 SP3

Total number of Ethernet packets received from the subscriber on the specified PVC and discarded due to upstream policing. Valid from: EDA 2.2 SP3

This parameter resets all the trafStatLogiPortErrors traffic statistics of the IPDSLAM to zero. Valid from: EDA 2.2 SP3 Enumeration: 'clear': 1.

This table contains tslpClearStat parameter which resets the upstream and downstream Logical port traffic statistics of the IPDSLAM to zero. Valid from: EDA 2.2 SP3

An entry in the trafStatLogiPortClearTable. Valid from: EDA 2.2 SP3

This parameter resets all the following Logical port traffic statistics of the IPDSLAM to zero. - peaBridgeIpDslam::trafStatLogiPortMain - peaBridgeIpDslam::trafStatLogiPortErrors. Valid from: EDA 2.2 SP3 Enumeration: 'clear': 1.