No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

NE40E V800R010C10SPC500 Configuration Guide - User Access 01

This is NE40E V800R010C10SPC500 Configuration Guide - User Access
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuring PPPoEv6 Access Services

Configuring PPPoEv6 Access Services

In PPPoEv6 access mode, a terminal is required to support the PPPoEv6 dial-up function.

Configuring an Address Allocation Mode

The address allocation modes supported by the NE40E include NDRA, DHCPv6(IA_NA), DHCPv6(IA_PD), DHCPv6(IA_NA)+PD(IA_PD), and NDRA+DHCPv6(IA_PD). One of them can be configured based on networking conditions.

Context

The address allocation mode varies according to the CPE working mode. For details, see the following table.
CPE Working Mode Scenario IPv6 Address Configuration Mode
Bridging mode The host initiates a connection request. The CPE transparently forwards the user request packet, and the NE40E allocates an IPv6 address to the host. NDRA
DHCPv6(IA_NA)
Unnumbered routing mode The CPE initiates a connection request. After receiving the request, the NE40E allocates a prefix to the CPE to generate IPv6 addresses for the hosts attached to the CPE. DHCPv6(IA_PD)
Numbered routing mode The CPE initiates a connection request. After receiving the request, the NE40E allocates an IPv6 address to the WAN interface on the CPE and a prefix to generate IPv6 addresses for the hosts attached to the CPE. DHCPv6(IA_NA)+PD(IA_PD)
NDRA+DHCPv6(IA_PD)
NOTE:
  • Layer 2 IPv6 leased-line access equals the situation where the CPE works in unnumbered or numbered routing mode.

  • Layer 3 users of a leased line obtain their addresses from the access router. The NE40E is in charge of only authentication and accounting, not address allocation.

If an IPv4 network is upgraded to an IPv6 network, the CPE working mode and authentication mode do not need to be changed unless there are special service requirements. In PPP authentication mode, either ND or DHCPv6 can be used for address authentication. In bind authentication mode, using DHCPv6 for address allocation is recommended. In 802.1X or Web authentication mode, using DHCPv6 for address allocation is recommended if user terminals support DHCPv6.

In addition to choosing an address allocation mode, perform the following steps on the NE40E if needed:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run aaa

    The AAA view is displayed.

  3. Run domain domain-name

    A domain is created, and the AAA domain view is displayed.

  4. Run user-basic-service-ip-type { ipv4 | ipv6 | ipv6-pd } *

    The IP type that is used for the services of users logging in from the domain is specified. If address allocation of the specified IP type fails, users are not allowed to log in.

  5. (Optional) Run ipv6 nd ra haltNE40E

    The NE40E is suppressed from sending RA messages to IPv6 access users.

  6. (Optional) Run ppp address-release separate

    PPP dual-stack users can go offline from a single stack.

    The ppp address-release separate and any-address-release offline commands are mutually exclusive.

    The ppp address-release separate command takes effect for both PPPoX and L2TP users.

  7. Run commit

    The configuration is committed.

Configuring a Virtual Template

Layer 2 protocols cannot directly carry each other. Before configuring PPPoE access, create a virtual template (VT).

Context

Layer 2 protocols, such as PPP can communicate only over a virtual access (VA) session. A VA session, however, cannot be manually created or configured. Instead, a VA session is automatically generated after PPPoE services are configured and PPPoE parameters are configured in a VT.

Based on interface parameters defined in a VT, a device can automatically create VA interfaces for Layer 2 communication.

  • PPP packets are encapsulated based on parameters configured in a VT. A VT defines NCP parameters, such as IP addresses and upper-layer application protocols.

  • A VA session transmits data between the local and remote ends based on parameters defined in a VT.

When a VT is used for PPPoE services, the link layer protocol can only be PPP, and the network layer protocol can only be IP.

Before deleting a VT, ensure that the VT is not in use and the VA session automatically generated upon VT creation has been deleted.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface virtual-template virtual-template-number

    A VT is created and its view is displayed, or the view of an existing VT is displayed.

  3. Run ppp authentication-mode { auto | { pap | chap | mschapv1 | mschapv2 } * }

    A PPP authentication mode is configured.

  4. (Optional) Perform the following steps to configure PPP negotiation parameters:

    • Run ppp timer { negotiate seconds | retransmit retry-times } *

      A PPP negotiation timeout period and the maximum number of retransmission times allowed are configured.

    • Run ppp delay-lcp-negotiation [ force ]

      Delayed LCP packet transmission is configured.

    • Run ppp keepalive { interval interval-time | retransmit times | response-timeout response-timeout-time } * [ datacheck | no-datacheck ]

      A PPP detection interval and the maximum number of retransmission times allowed are configured.

    • Run ppp keepalive adjustment { system-state | retransmit }

      Adjustment of the number of PPP detection times is enabled.

    • Run mtu mtu

      An MTU is configured in the VT.

    • Run ppp mru mru

      An MRU is configured for PPP negotiation.

    • Run pppoe-motm motm-value

      The device is configured to encapsulate clock synchronization information to the MOTM tag in a PPPoE active discovery message (PADM).

    • Run quit

      Return to the system view.

    • Run pppoe ppp-max-payload enable

      The device is enabled to negotiate the MRU in compliance with standard protocols.

  5. (Optional) Run ppp chap user user-name

    A user name is specified.

  6. Run commit

    The configuration is committed.

Binding the Virtual Template to an Interface

Bind a VT to an interface so that data on the interface can be transmitted based on parameters defined in the VT.

Context

After a VT is configured, bind it to an interface. The type of the interface to which a VT is bound varies depending on the user access type.

  • The VT configured for PPPoE services must be bound to a main interface.

  • The VT configured for PPPoEoVLAN services must be bound to a sub-interface.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number [ . subinterface-number ]

    The interface or sub-interface view is displayed.

    Specify a main interface for PPPoE access users and a sub-interface for PPPoEoVLAN access users.

  3. Run pppoe-server bind virtual-template vt-number

    A VT is bound to the interface.

  4. Run commit

    The configuration is committed.

Binding a Sub-interface to a VLAN

To restrict broadcast packets on a LAN and enhance the LAN security or create virtual groups, you need to configure VLANs. VLANs are applicable to only Ethernet sub-interfaces.

Context

If users access the network by using a sub-interface, the sub-interface needs to be bound to a VLAN.

You can bind a sub-interface to a VLAN or configure QinQ on a sub-interface. When binding a sub-interface to a VLAN, you need the following parameters:

  • Sub-interface number
  • VLAN ID
  • QinQ ID
NOTE:
  • On each main interface, you can set the user-vlan any-other on only one sub-interface. On one sub-interface, user-vlan any-other cannot be set together with user-vlan start-vlan nor user-vlan qinq.
  • The user-vlan command cannot be configured on a sub-interface of a Layer 2 interface.
  • If dot1q termination, QinQ termination, QinQ stacking, or vlan-type dot1q has been configured on a sub-interface, the user-vlan cannot be configured on this sub-interface.
  • Different sub-interfaces cannot be configured with user-side VLANs with the same VLAN ID.

Perform the following steps on the NE40E:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number.subinterface-number

    A sub-interface is created and the sub-interface view is displayed.

  3. Run user-vlan { start-vlan [ end-vlan ] [ qinq start-qinq-id [ end-qinq-id ] ] | any-other }

    A user-side VLAN is created.

  4. Run commit

    The configuration is committed.

Configuring a BAS Interface

If an interface is used for broadband user access, you need to configure the interface as a BAS interface and set the access type and other attributes.

Context

When configuring a BAS interface, you need the following parameters:

  • BAS interface number

  • Access type and authentication scheme

  • Specified domains for the BAS interface
    • Default authentication domain

      If no domain name is entered during user authentication, the NE40E regards the user as a member in the default authentication domain by default.

    • Roaming domain

      The roaming domain is used for users whose domain names are unidentified. If a user enters an unidentified domain name during authentication, the NE40E classifies the user as a roaming domain user and conducts the following authentication.

    • Domain for user access

      If a domain for user access is specified on a BAS interface, users can log in to the NE40E from the domain. If they log in to the NE40E from other domains, the NE40E will deny their access requests.

    • Domain denying user access

      If a domain denying user access is specified on a BAS interface, users cannot log in to the NE40E from the domain. If they log in to the NE40E from other domains, the NE40E will accept their access requests.

  • Additional functions of the BAS interface

    • Access triggered by IPv6 packets

    • Access triggered by NS or NA packets

    • BAS interface name

      Knowing the BAS interface name facilitates memorization and management.

    • Accounting packet copy

      The accounting packet copy function sends accounting information to two RADIUS servers at the same time and waits for their responses. The function is used when original accounting information needs to be stored on multiple devices (for example, the multi-carrier networking scenario). After the function is configured, accounting packets are sent to two RADIUS servers simultaneously (as the original accounting information) to facilitate later account settlement.

  • Packet processing mode

    • access-line-id

      On a broadband telecommunication network, the DSLAM obtains DHCP packets and adds access-line-id information to them. access-line-id records information about the user's physical interface. As the access-line-id information is transmitted to the NE40E, DHCP server, and RADIUS server, the devices are informed of the user location. The management system then implements proper security and address allocation strategies based on the user location information.

    • link-account

      If only RADIUS accounting is used, the RADIUS accounting server uses VLAN/PVC descriptions to identify common Layer 2 users and uses interface descriptions to identify Layer 3 leased line users. The BRAS encapsulates the descriptions into the Class attributes and sends it to the RADIUS accounting server.

Perform the following steps on the NE40E.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number [ .subinterface-number ]

    The interface view is displayed.

  3. Run bas

    A BAS interface is created, and the BAS interface view is displayed.

    You can configure an interface as the BAS interface by running the bas command in the interface view. An Ethernet interface or its sub-interface, or an Eth-Trunk interface or its sub-interface can be set to a BAS interface.

  4. Configure the access type.

    • Run access-type layer2-subscriber [ default-domain [ authentication dname ] ]

      The access type and relevant attributes are configured for Layer 2 access users.

    The access type cannot be configured on the Ethernet interface that is added to an Eth-Trunk interface. You can configure the access type only on the Eth-Trunk interface.

  5. Configure the authentication mode.

    Run authentication-method ppp [ web ]

    or run authentication-method-ipv6 ppp [ web ]

    PPP or PPP Web authentication is configured.

  6. (Optional) Specify domains on the BAS interface.

    NOTE:

    The permit-domain command, deny-domain command, deny-domain-list command, and permit-domain-list command cannot be configured on the same BAS interface.

    • Configure the default pre-authentication domain.

      Run default-domain pre-authentication domain-name

      The default pre-authentication domain is specified.

    • Configure the default authentication domain.

      Run default-domain authentication [ force | replace ] domain-name

      The default authentication domain is specified.

      NOTE:

      Run default-domain authentication ppp-user domain-name

      The default authentication domain for PPP users is specified.

      • If the default-domain authentication ppp-user domain-name command is configured, the authentication domain specified in this step is used as the default authentication domain for PPP users.
      • If the default-domain authentication ppp-user domain-name command is not configured but the default-domain authentication [ force | replace ] domain-name command is configured, the authentication domain specified using the default-domain authentication [ force | replace ] domain-name command is used as the default authentication domain for PPP suers.
      • If neither of the commands is configured, the default authentication domain for PPP users is default1.
    • Configure the roaming domain.

      Run roam-domain domain-name

      The roaming domain is specified.

    • Configure the domain for user access.

      Run permit-domain domain-name &<1-16>

      A domain for user access is specified.

    • Configure the domain denying user access.

      Run deny-domain domain-name&<1-16>

      A domain denying user access is specified.

      Or, run deny-domain-list

      A list of domains denying user access is configured.

  7. (Optional) Configure additional functions of the BAS interface.

    • Configure access triggered by packets.

      • Run ipv6-trigger

        Access triggered by IPv6 packets is configured.

      • Or, run nd-trigger

        Access triggered by NS or NA packets is configured.

    • Configure the accounting packet copy function.

      Run accounting-copy radius-server radius-name

      The accounting packet copy function is enabled.

    • Configure the user detection interval.

      Run user detect retransmit number interval time

      The user detection interval is configured.

    • Block the BAS interface.

      Run block [ start-vlan { start-vlan [ end-vlan end-vlan ] [ qinq pe-vlan ] | any qinq start-qinq-vlan [ end-qinq-vlan ] } | pvc start-vpi/start-vci [ end-vpi/end-vci ] ]

      The BAS interface is blocked.

    • Limit the number of users on the BAS interface.

      Run access-limit number

      The number of users on the BAS interface is limited.

      If the command is run and the VLANinformation is specified, the number of users in specified VLAN(s) on the BAS interface is limited.

      If the command is run and the VLAN information is not specified, the number of users in each VLAN/PVC on the BAS interface is limited. If the two types of configurations coexist on a BAS interface, they do not conflict. The number of users in the specified VLAN/PVC is subject to the limit set for the specified VLAN. The number of users in any one of the other unspecified VLANs is subject to the limit set for each VLAN on the BAS interface.

  8. (Optional) Configure the packet processing mode.

    • Configure the method of processing access-line-id information.

      Run the client-option82 [ { basinfo-insert { cn-telecom | version3 } | version1 } ] or client-access-line-id [ basinfo-insert cn-telecom | version1 ] command to configure the NE40E to trust the access-line-id information sent from the client.

      Or, run the basinfo-insert cn-telecom command to configure the NE40E to distrust the access-line-id information sent from the client and insert the access-line-id information in the format defined by China Telecom.

      Or, run the basinfo-insert version2 to configures the router to insert the access-line-id information in the format defined by version2 if the router does not trust the access-line-id information sent from the DHCP client.

      The router will parse and transmit access-line-id information based on the following configurations:
      • Run the option82-relay-mode dslam or access-line-id dslam { auto-identify | config-identify } command to allow the router to extract information from the access-line-id field in the packet sent from the DSLAM and add the information to Agent-CircuitID and Agent-RemoteID attributes sent to the RADIUS server. Or, run the option82-relay-mode include or access-line-id include { allvalue | { agent-circuit-id | agent-remote-id [ separator ] }* } command to allow the NAS-Port-Id attribute sent to the RADIUS server to contain access-line-id information.
      • Run the option82-relay-mode subopt or access-line-id translate { agent-circuit-id { hex | string } | agent-remote-id { hex | string } command to configure the format of Agent-CircuitID or Agent-RemoteID information.

      Or, run vbas vbas-mac-address [ auth-mode { ignore | reject } ]

      The function of locating a user through the virtual BAS (VBAS) is enabled.

    • Configure the method of processing link-account information.

      Run link-account resolve

      The accounting-request packet carrying link-account information is sent to a RADIUS server.

      The RADIUS No.25 attribute for accounting-request packets sent by the device to a RADIUS accounting server is affected.

      An interface fills in the link-account information in the RADIUS No.25 attribute class if both the following situations are met:
      • Users getting online from the interface do not need to be authenticated and RADIUS accounting is configured on the interface.
      • For common Layer 2 users, VLANs and VLAN descriptions are configured on the interface, or PVCs and PVC descriptions are configured on the interface.

  9. Run commit

    The configuration is committed.

(Optional) Configuring Refined IPv6 Route Advertisement

Refined IPv6 route advertisement can classify routes and advertise them to different networks.

Context

IPv6 network segment routes and address pool routes are classified based on tags and imported using routing policies. This process allows various routes to be advertised to specific networks. IPv6 network segment routes are generated based on Delegated-IPv6-Prefix attributes that are delivered by a RADIUS server.

Procedure

  • Configure a tag value of a route for a specified type of address pool, such as local or remote address pools.
    1. Run system-view

      The system view is displayed.

    2. Run ipv6 unr { delegated-ipv6-prefix-tag tag-value | delegated-pool-tag tag-value | framed-ipv6-address-tag tag-value | framed-ipv6-prefix-tag tag-value | framed-ipv6-route-tag tag-value | local-pool-tag tag-value | remote-pool-tag tag-value } *

      The route tag is configured.

  • Configure a tag value of a route for a single address pool.
    1. Run system-view

      The system view is displayed.

    2. Run ipv6 pool (system view)

      The IPv6 address pool view is displayed.

    3. Run unr tag tag-value

      The route tag is configured.

Follow-up Procedure

Create a routing policy. Specify a route tag to classify routes. Use OSPFv3 or BGP+ to import different routes. For details, see Routing Policy Configuration.

(Optional) Configuring the PPP Magic Number Check Function

You can configure the PPP magic number check function to detect whether a PPPoE user stays online after the user logs in.

Context

After a PPPoE user goes online, the device periodically sends Echo Request packets to the client.

When receiving an Echo Reply packet from the user, the device compares the magic number carried in the packet with that learned during LCP negotiation. If the two magic numbers are the same, the user is considered online. Otherwise, the user is considered offline.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run ppp keepalive strict-check magic-number

    The PPP magic number check function is enabled so that the device compares the magic number in a received Echo Reply packet with that learned during LCP negotiation.

  3. Run commit

    The configuration is committed.

Verifying the PPPoXv6 Access Service Configuration

After configuring the PPPoXv6 access service, check the PPPoXv6 access configurations.

Procedure

  • Run the display access-user command to check information about all access users. You can specify the command parameters to view the specific user information.
  • Run the display sub-interface interface-type interface-number pevlan pe-vlan-id [ cevlan ce-vlan-id ] command to check information about a sub-interface bound to a specified VLAN on an interface.
  • Run the display bas-interface command to check information about the BAS interface.
  • Run the display vlan-statistics interface interface-type interface-number.subinterface-number pevlan pe-vlan-id [ cevlan ce-vlan-id ] [ verbose ] command to check statistics about traffic and PPP packets on a specified sub-interface bound to a specified VLAN.

    NOTE:

    The display vlan-statistics interface interface-type interface-number.subinterface-number pevlan pe-vlan-id [ cevlan ce-vlan-id ] [ verbose ] command can be configured only through a PAF file.

  • display vlan-statistics interface interface-type interface-number pevlan pe-vlan-id command to check statistics about traffic on a specified interface bound to a specified VLAN.
  • Run the display ppp slot slot-number chasten-user [ mac-address mac-address ] command to check information about the PPP users that are forbidden to access the NE40E.
  • Run the display ppp { user-id user-id | username username | ip-address ipv4-address [ vpn-instance instance-name ] | ipv6-address ipv6-address [ vpn-instance instance-name ] | circuit-id circuit-id-text | remote-id circuit-id-text } command to check information about the PPP status.

    NOTE:
    Configuring the ui-mode type1 command in the system view influences the output format of the display command.

Example

Run the display access-user command. If the IPoEv6 access service is configured successfully, and you can view information about all access users.
<HUAWEI> display access-user
 ------------------------------------------------------------------------------
  Total users                        : 9
  IPv4 users                         : 9
  IPv6 users                         : 0
  Dual-Stack users                   : 0
  Lac users                          : 0
  RUI local users                    : 0
  RUI remote users                   : 0
  Wait authen-ack                    : 0
  Authentication success             : 9
  Accounting ready                   : 9
  Accounting state                   : 0
  Wait leaving-flow-query            : 0
  Wait accounting-start              : 0
  Wait accounting-stop               : 0
  Wait authorization-client          : 0
  Wait authorization-server          : 0
  ------------------------------------------------------------------------------
  Domain-name                        Online-user
  ------------------------------------------------------------------------------
  default0                           : 0
  default1                           : 0
  default_admin                      : 0
  wq                                 : 0
  chen                               : 0
  isp7                               : 0
  gaoli                              : 0
  ly                                 : 0
  test                               : 0
  lsh                                : 9
  ------------------------------------------------------------------------------
  The used CID table are             :
  20-28
  ------------------------------------------------------------------------------
Run the display sub-interface interface-type interface-number pevlan pe-vlan-id [ cevlan ce-vlan-id ] command, you can view information about the sub-interface bound to VLAN 1000 on Eth-Trunk 11.
<HUAWEI> display sub-interface Eth-Trunk11 pevlan 1000
    Sub-interface: Eth-Trunk11.1000
    Sub-interface-status: UP
    PeVlan/CeVlan: 1000/0
    The BAS function has been enabled
Run the display bas-interface command, you can view brief information about all BAS interfaces.
<HUAWEI> display bas-interface
---------------------------------------------------------------------------
   Interface                BASIF-access-type       config-state   access-number
  ---------------------------------------------------------------------------
   Eth-Trunk0               Layer2-subscriber       Updated        0
   Eth-Trunk0.1             Layer2-subscriber       Updated        1
   Eth-Trunk0.1234          Layer2-subscriber       Updated        0
  ----------------------------------------------------------------------
  Total 3 BASIF is configured                                          
Run the display vlan-statistics interface interface-type interface-number pevlan pe-vlan-id command, you can view traffic statistics on the interface GE 1/0/1.
<HUAWEI> display vlan-statistics interface GigabitEthernet 1/0/1
  Interface Name: GigabitEthernet1/0/1  
  input: 0 packets, 0 bytes
  output: 0 packets, 0 bytes
  ipv4 input: 0 packets, 0 bytes
  ipv4 output: 0 packets, 0 bytes
  ipv6 input: 0 packets, 0 bytes
  ipv6 output: 0 packets, 0 bytes
Run the display ppp slot slot-number chasten-user command, you can view information about the users that are forbidden to access the interface board in slot 1.
<HUAWEI> system-view
[HUAWEI] display ppp slot 1 chasten-user
 ------------------GLOBAL PPP CHASTEN USERS SLOT 1 ---------------------
 To be possibly blocked User Num: 0     (online-fail)
 To be possibly blocked User Num: 0     (quick-offline)
 To be possibly blocked User Num by Option105: 0     (online-fail)
 To be possibly blocked User Num by Option105: 1     (quick-offline)
 (1):MAC 00-02-01-01-01-01 Option105(circuitid:123 remoteid:abcde) will be free 
after 89s (quick-offline)
 Blocked User Num : 0     (online-fail)
 Blocked User Num : 1     (quick-offline)
 ------------------PPPOE VLAN CHASTEN USERS SLOT 1 ---------------------
 To be possibly blocked User Num: 0     (online-fail)
 To be possibly blocked User Num: 0     (quick-offline)
 To be possibly blocked User Num by Option105: 0     (online-fail)
 To be possibly blocked User Num by Option105: 0     (quick-offline)
 Blocked User Num : 0     (online-fail)
 Blocked User Num : 0     (quick-offline)
If the ui-mode type1 command is not configured, run the display ppp user-id user-id command to display PPP configurations.
<HUAWEI> display ppp user-id 100
  --------------------------------------------------------------------------    
  Basic information of user                                                     
  --------------------------------------------------------------------------    
  User Name              :huawei@test1                                         
  Session ID             :1                                                     
  User Mac               :0016-ecaa-975b                                        
  Interface              :Eth-Trunk3.409                                        
  PeVlan/CeVlan          :409/0                                                 
  VPI/VCI                :0/0                                                   
  IP                     :10.0.0.200                                           
  Gateway                :10.0.0.1                                             
  User IP Netmask(Client) :255.255.255.0
  User IP Netmask(Radius):255.255.255.128
  User IP Netmask(Result) :255.255.255.128                                     
  Primary DNS            :0.0.0.0                                               
  Second  DNS            :0.0.0.0                                               
  IPV6 Interface IDType  :AUTO                                                  
  IPv6 Local InterfaceID :2 e0:fcff:fe5f:d7ae                                   
  IPv6 Peer InterfaceID  :2 16:ec0 :1 aa:975b                                   
  --------------------------------------------------------------------------    
  LCP  information                                                              
  --------------------------------------------------------------------------    
  Authentication         :CHAP                                                  
  MTU                    :1480                                                  
  MRU                    :1492                                                  
  MagicNumber            :0x2a954e9b                                            
  CalledNumber           :                                                      
  CallingNumber          :                                                      
  Keep Alive Time        :300                                                   
  Retransmit Times       :10                                                    
  --------------------------------------------------------------------------    
  LAC-LNS  information                                                          
  --------------------------------------------------------------------------    
  Lac-PeerIp             :0.0.0.0                                               
  Lac-PeerTunnelId       :0                                                     
  Lac-PeerSessionId      :0                                                     
  Lac-LocalIp            :0.0.0.0                                               
  Lac-LocalTunnelId      :0                                                     
  Lac-LocalSessionId     :0                                                     
  Lac-SrcUDPPort         :0                                                     
  Lac-DstUDPPort         :0                                                     
                                                                                
  Lns-PeerIp             :0.0.0.0                                               
  Lns-PeerTunnelId       :0                                                     
  Lns-PeerSessionId      :0                                                     
  Lns-LocalIp            :0.0.0.0                                               
  Lns-LocalTunnelId      :0                                                     
  Lns-LocalSessionId     :0                                                     
  Lns-SrcUDPPort         :0                                                     
  Lns-DstUDPPort         :0                                                     
  --------------------------------------------------------------------------     
Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055031

Views: 19292

Downloads: 83

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next