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

NE20E-S2 V800R010C10SPC500 Configuration Guide - LAN Access and MAN Access 01

This is NE20E-S2 V800R010C10SPC500 Configuration Guide - LAN Access and MAN 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 a VLAN Tag Termination Sub-interface to Transmit the VPN Service

Configuring a VLAN Tag Termination Sub-interface to Transmit the VPN Service

Virtual Private Network (VPN) services are classified into L2VPN services and L3VPN services. You can configure VLAN tag termination sub-interfaces on the PEs to connect VPNs to enable the interworking between the CEs and users.

Applicable Environment

Table 9-8 shows a typical application scenario in which VLAN tag termination sub-interfaces transmit VPN services.

Table 9-8 VLAN tag termination sub-interfaces transmitting VPN services

VPN Service

Application

L2VPN

When a VLAN tag termination sub-interface is used to access a L2VPN network, this sub-interface needs to be bound to a Virtual Switching Instance (VSI) or Virtual Private Wire Service (VPWS) to enable Layer 2 communication.

L3VPN

When a VLAN tag termination sub-interface is used to access a L3VPN network, this sub-interface needs to be bound to a VPN instance to enable Layer 3 communication.

Pre-configuration Task

Before you configure the VLAN tag termination sub-interface to transmit VPN services, plan user VLANs so that packets received by VLAN tag termination sub-interfaces carry one or two VLAN tags.

Configuration Procedures

Figure 9-9 Flowchart for configuring VLAN tag termination sub-interfaces to transmit VPN services

Configuring a VLAN Tag Termination Sub-interface

A virtual local area network (VLAN) tag termination sub-interface can be a sub-interface for dot1q VLAN tag termination or a sub-interface for QinQ VLAN tag termination. In dot1q/QinQ termination, a device identifies whether a packet has one tag or two tags. The device then forwards the packet after stripping one or both tags or discards the packet.

Context

An increasing number of QinQ encapsulation and termination modes have been developed to distinguish users or services and reduce the use of virtual local area network (VLAN) IDs. These QinQ encapsulation and termination modes enable carriers to implement refined operation.

Users may communicate over various types of Layer 2 virtual private networks (L2VPNs), such as a virtual private wire service (VPWS) or virtual private LAN service (VPLS). To achieve more flexibility in managing packets for these users, you can configure sub-interfaces for QinQ VLAN tag termination on edge devices on the L2VPN and configure the attributes of the sub-interfaces to provide L2VPN access.

Sub-interfaces for QinQ VLAN tag termination can access VPWS or VPLS in symmetrical or asymmetrical mode. User packets are sent to the L2VPN in different modes after being processed by the PE, as described in Table 9-9 and Table 9-10.

Table 9-9 Packet processing on an inbound interface

Inbound Interface Type

VPWS/VPLS

Ethernet Encapsulation

VLAN Encapsulation

Symmetry mode

Removes the outer tag.

Keeps both inner and outer tags unchanged.

Asymmetrical mode

Removes both inner and outer tags.

Removes both inner and outer tags and adds another tag.

Table 9-10 Packet processing on an outbound interface

Outbound Interface Type

VPWS/VPLS

Ethernet Encapsulation

VLAN Encapsulation

Symmetry mode

Adds an outer tag.

Replaces the outer tag.

Asymmetrical mode

Adds two tags.

Removes the existing tag, and adds two tags.

NOTE:
To configure VLAN encapsulation or Ethernet encapsulation, run the encapsulation (VSI view) command.
  • VLAN encapsulation

    Each Ethernet frame transmitted between CEs and PEs carries a VLAN tag called a Provider-Tag (P-tag). The tag is a service delimiter required by a carrier for user differentiation.

  • Ethernet encapsulation

    Ethernet frames transmitted between CEs and PEs do not necessarily carry VLAN tags. If an Ethernet frame carries a VLAN tag, the tag is an internal VLAN tag called a User-Tag (U-tag) in user packets. The U-tag is carried in a packet before the packet is sent to a CE. The U-tag is used by the CE to identify the packet, but PEs do not recognize U-tags.

By default, the encapsulation type is VLAN.

Procedure

  • Configure the sub-interface for dot1q VLAN tag termination.

    1. Run system-view

      The system view is displayed.

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

      The view of an Ethernet sub-interface at the user-side of a PE is displayed.

    3. (Optional) Create a user VLAN group.

      1. Run vlan-group group-id

        A user VLAN group is created.

      2. Run group mode { single | multiple }

        The working mode of the VLAN group is configured.

        • single: A VLAN group is considered as a user. This means that you cannot collect statistics about QinQ packets or deploy quality of service (QoS) policies based on a VLAN or a VLAN range.
        • multiple: VLANs and VLAN ranges in a VLAN group are considered as different users. This means that you can collect statistics about QinQ packets or deploy QoS policies based on a VLAN or VLAN range to implement refined management.
      3. Run quit

        Return to the view of the Ethernet sub-interface at the user-side of the PE.

      NOTE:

      Configuring a VLAN group allows you to achieve the following purposes:

      • Deploy QoS policies based on services or users so that higher priority service traffic is preferentially forwarded, improving user experience.
      • View statistics about QinQ packets to check whether a device is functioning properly.
    4. Run control-vid vid dot1q-termination [ rt-protocol ] or encapsulation dot1q-termination [ rt-protocol ]

      The encapsulation type for a VLAN tag termination sub-interface is configured to be dot1q.

      Specify rt-protocol so that the sub-interface for dot1q VLAN tag termination supports routing protocols.

    5. Run either of the following commands:
      • To configure a sub-interface for dot1q VLAN tag termination, run the dot1q termination vid low-pe-vid [ to high-pe-vid ] [ vlan-group group-id ] command.
      • To configure a sub-interface for dot1q VLAN tag termination and a matching policy for the sub-interface, run the dot1q termination vid low-pe-vid [ to high-pe-vid ] { 8021p { 8021p-value1 [ to 8021p-value2 ] } &<1-8> | dscp { dscp-value1 [ to dscp-value2 ] } &<1-10> | eth-type pppoe | default } [ vlan-group group-id ] command.

      NOTE:
      • If you do not configure a matching policy, the sub-interface for dot1q VLAN tag termination terminates the VLAN tags of packets carrying the specified VLAN ID. If you configure a matching policy, the sub-interface for dot1q VLAN tag termination terminates the VLAN tags of packets carrying the specified VLAN ID+802.1p value/DSCP value/EthType.

      • After the dot1q termination vid low-pe-vid [ to high-pe-vid ] [ vlan-group group-id ] command is run in the Ethernet sub-interface view, the specified VLAN range belongs to the sub-interface, and any VLAN ID in the VLAN range cannot be configured together with the 802.1p value/DSCP value/EthType on other sub-interfaces.

    6. Run commit

      The configuration is committed.

  • Configure the sub-interface for QinQ VLAN tag termination.

    1. Run system-view

      The system view is displayed.

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

      The view of an Ethernet sub-interface at the user-side of a PE is displayed.

    3. (Optional) Create a user VLAN group.

      1. Run vlan-group group-id

        A user VLAN group is created.

      2. Run group mode { single | multiple }

        The working mode of the VLAN group is configured.

        • single: A VLAN group is considered as a user. This means that you cannot collect statistics about QinQ packets or deploy quality of service (QoS) policies based on a VLAN or a VLAN range.
        • multiple: VLANs and VLAN ranges in a VLAN group are considered as different users. This means that you can collect statistics about QinQ packets or deploy QoS policies based on a VLAN or VLAN range to implement refined management.
      3. Run quit

        Return to the view of the Ethernet sub-interface at the user-side of the PE.

      NOTE:

      Configuring a VLAN group allows you to achieve the following purposes:

      • Deploy QoS policies based on services or users so that higher priority service traffic is preferentially forwarded, improving user experience.
      • View statistics about QinQ packets to check whether a device is functioning properly.
    4. Run control-vid vid qinq-termination [ local-switch | rt-protocol ] or encapsulation qinq-termination [ local-switch | rt-protocol ]

      The encapsulation type for a VLAN tag termination sub-interface is configured to be QinQ.

      • Specify local-switch so that the sub-interface for QinQ VLAN tag termination supports local switching.

      • Specify rt-protocol so that the sub-interface for QinQ VLAN tag termination supports routing protocols.

    5. (Optional) Run qinq termination l2 { asymmetry | symmetry [ user-mode ] }

      The termination mode is configured for the sub-interface for QinQ VLAN tag termination that provides L2VPN access.

      NOTE:

      This step takes effect only on sub-interfaces for QinQ VLAN tag termination that provide L3VPN access. Therefore, before you configure a sub-interface for QinQ VLAN tag termination that provides L2VPN access, configure the termination mode of the sub-interface.

      • If the qinq termination l2 symmetry command is used on a sub-interface for QinQ VLAN tag termination, the sub-interface connects to the L2VPN in symmetrical mode. MAC address learning is performed only on the outer tags carried in packets. The sub-interface sends inner tags as part of the data to the peer. To configure QoS for inner tags, run the qinq termination l2 symmetry user-mode command.

      • If the qinq termination l2 asymmetry command is used on a sub-interface for QinQ VLAN tag termination, the sub-interface connects to the L2VPN in asymmetrical mode. MAC address learning is performed on both inner and outer tags carried in packets. The sub-interface does not send inner tags as part of the data to the peer.

      • If the qinq termination l2 asymmetry command is run on a sub-interface for QinQ VLAN tag termination, the sub-interface can terminate single inner and outer VLAN tags carried in packets but cannot terminate VLAN tag ranges.

    6. Run qinq termination pe-vid pe-vid [ to high-pe-vid ] ce-vid ce-vid [ to high-ce-vid ] [ vlan-group group-id ]

      The VLAN tag termination function is configured for the sub-interface for QinQ VLAN tag termination.

      After you specify rt-protocol, the sub-interface terminates double-tagged packets, and both inner and outer tags must be specific VLAN IDs.

    7. Run commit

      The configuration is committed.

(Optional) Configuring a PW-Tag Action

This section describes how to configure a PW-tag action so that a PE changes the P-Tag of packets to be forwarded over a PW in tagged mode to ensure normal communication with non-Huawei devices on an L2VPN network.

Context

As shown in Figure 9-10, CE1 and CE2 are connected to the L2VPN network through PE sub-interfaces, PE1 and CE1 are Huawei devices, and PE2 and CE2 are non-Huawei devices.

When a PE transmits multiple services over one PW, the PE adds different P-Tags to packets of different services to isolate the packets on the L2VPN network. When the packets reach the sub-interfaces of another PE on the other end of the PW, each sub-interface accepts only those packets carrying the same P-Tag as that specified on the sub-interface.

However, because the P-Tags on PE1 and PE2 may be different, PE1 cannot communicate with PE2, and users from user networks connected to CE1 and CE2 cannot communicate with each other.

Figure 9-10 Networking for accessing an L2VPN through sub-interfaces

To address the problem, configure a PW-tag action on the user-side sub-interface of PE1. The PE1 sub-interface changes the P-Tag of packets to that on PE2 before forwarding the packets over the PW. This allows PE1 to communicate with PE2.

Table 9-11 provides the default P-Tag values and the P-Tag values after the PW-tag action.

Table 9-11 P-Tag values

Sub-Interface Type

Default P-Tag Value

P-Tag Value After the PW-Tag Action

Dot1q sub-interface

VLAN ID in a packet

New VLAN ID

Sub-interface for dot1q VLAN tag termination

Sub-interface for QinQ VLAN tag termination

Outer VLAN ID in a packet

QinQ stacking sub-interface

Minimum VLAN ID in the VLAN ID range specified on the sub-interface

QinQ mapping sub-interface

Fixed VLAN ID in the system

Procedure

  1. Run system-view

    The system view is displayed.

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

    The view of a user-side sub-interface on a PE is displayed.

  3. Run pw-tag { vlan-id | inner-vlan | outer-vlan } [ 8021p { 8021p-value | inner-vlan | outer-vlan } ]

    A PW-tag action is configured so that the sub-interface changes the P-Tag of packets before forwarding the packets over the PW in tagged mode.

  4. Run commit

    The configuration is committed.

Configuring VPN Services

After you configure the VLAN tag termination sub-interface, you need to configure VPN services so as to enable users to communicate with each over an L2VPN or an L3VPN.

Context

Sub-interfaces for VLAN tag termination cannot forward broadcast packets. They automatically discard broadcast packets they receive. To allow VLAN tag termination sub-interfaces to forward broadcast packets, run the arp broadcast enable command on the sub-interfaces to enable the ARP broadcast function.

When an IP packet is sent on a VLAN tag termination sub-interface without a corresponding ARP entry, the following may occur:
  • If the access device supports automatic forwarding of ARP packets, the packets are forwarded even if the ARP broadcast function is disabled on the VLAN tag termination sub-interface.

  • If the access device does not support automatic forwarding of ARP packets:

    • The system discards the IP packet if the arp broadcast enable command is not configured on the VLAN tag termination sub-interface. In this case, the route with the VLAN tag termination sub-interface as the outbound interface is considered a black hole route.

    • If the arp broadcast enable command is configured on the VLAN tag termination sub-interface, the system originates a tagged ARP broadcast packet and forwards it through the VLAN tag termination sub-interface.

When you enable or disable the ARP broadcast function on a VLAN tag termination sub-interface, the routing status of the sub-interface goes Down and then Up. This may result in route flapping on the entire network.

  • Configure L2VPN.

    For detailed information, see the chapters "VPWS Configuration" and "VPLS Configuration" in the HUAWEI NE20E-S2 Configuration Guide - VPN.

  • Configure L3VPN.

    For detailed information, see the chapter "BGP MPLS IP VPN Configuration" in the HUAWEI NE20E-S2 Configuration Guide - VPN.

Perform the following steps on the device that supports VPN services:

Procedure

  1. Run system-view

    The system view is displayed.

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

    The view of the VLAN tag termination sub-interface is displayed.

  3. Configure a VLAN tag termination sub-interface to transmit VPN services, as shown in Table 9-12.

    Table 9-12 VLAN tag termination sub-interfaces transmitting VPN services

    Service Type

    VLAN Tag Termination Sub-interface

    Description

    VPWS

    Run the mpls l2vc { ip-address | pw-template pw-template-name } * vc-id [ tunnel-policy policy-name | [ control-word | no-control-word ] | [ raw | tagged ] | access-port | ignore-standby-state ] * command to create a VPWS connection.

    • ip-interworking must be configured when Huawei devices interwork with each other over heterogeneous media.
    • ip-layer2 must be configured when Huawei devices interwork with non-Huawei devices over heterogeneous media.

    VPLS

    Run the l2 binding vsi vsi-name command to bind a VLAN tag termination sub-interface to a VSI instance.

    -

    L3VPN

    Run the ip binding vpn-instance vpn-instance-name command to bind a VLAN tag termination sub-interface to a VPN instance.

    -

  4. (Optional) Run the arp broadcast enable command to enable the ARP broadcast function on the VLAN tag termination sub-interface.

    NOTE:

    This step takes effect only on sub-interfaces for QinQ VLAN tag termination that provide L3VPN access.

  5. Run commit

    The configuration is committed.

Verifying the VPN Service Configuration on the VLAN Tag Termination Sub-interface

After you configure VPN services on the VLAN tag termination sub-interface, verify the configuration.

Prerequisites

The configurations of the VLAN tag termination sub-interface to transmit VPN services are complete.

Procedure

  • Run the display dot1q information termination [ interface interface-type interface-number [ .subinterface-number ] ] command to check information about the sub-interface for dot1q VLAN tag termination.
  • Run the display qinq information termination [ interface interface-type interface-number [ .subinterface-number ] ] command to check information about the sub-interface for QinQ VLAN tag termination.
  • View the configuration of the L2VPN in CCC mode.

    • Run the display vll ccc [ ccc-name | type { local | remote } ] command to check information about the CCC connection.

    • Run the display l2vpn ccc-interface vc-type ccc [ up | down ] command to check information about the interface in the Up or Down state.

  • View the configuration of the L2VPN in Martini mode.

    • Run the display mpls l2vc [ vc-id | interface interface-type interface-number ] command to check information about the Martini MPLS L2VPN connection on the PE.

    • Run the display mpls l2vc remote-info [ vc-id ] command to check information about the remote Martini MPLS L2VPN connection on the PE.

  • Run the display ip vpn-instance verbose [ vpn-instance-name ] command to check detailed information about the VPN instance.
  • Run the display bgp [ vpnv4 vpn-instance vpn-instance-name ] peer command to check information about the BGP peer.

Example

Run the display dot1q information termination command on a PE to view information about the sub-interface for dot1q VLAN tag termination. For example:
<HUAWEI> display dot1q information termination interface gigabitethernet 0/1/1.2
  GigabitEthernet 0/1/1.2
    L3VPN bound
    Total QinQ Num: 2
      dot1q termination vid 10
      dot1q termination vid 20 to 50 vlan-group 3
    Total vlan-group Num: 1
      vlan-group 3
    encapsulation dot1q-termination
Run the display qinq information termination command on a PE to view information about the sub-interface for QinQ VLAN tag termination. For example:
<HUAWEI> display qinq information termination interface gigabitethernet 0/1/1.1
  GigabitEthernet 0/1/1.1
    VSI bound
    Total QinQ Num: 2
      qinq termination pe-vid 10 ce-vid 10
      qinq termination pe-vid 20 to 30 ce-vid 40 to 50 vlan-group 2
    Total vlan-group Num: 1
      vlan-group 2
    encapsulation qinq-termination
  • After VPWS is configured:
    • Run the display vll ccc command. The command output shows that the CCC VC status is Up. For example:

      <HUAWEI> display vll ccc
      total  ccc vc : 1
      local  ccc vc : 1,  1 up
      remote ccc vc : 0,  0 up
      
      name: ce1-ce2, type: local, state: up,
      intf1: GigabitEthernet0/3/0 (up),access-port: false
      
      intf2: GigabitEthernet0/3/2 (up),access-port: false
      VC last up time : 2012/03/08 05:13:10
      VC total up time:  4 days, 5 hours, 11 minutes, 22 seconds
    • Run the display l2vpn ccc-interface vc-type ccc command. The command output shows that the VC type is CCC and that the CCC status is Up. For example:

      <HUAWEI> display l2vpn ccc-interface vc-type all
      Total ccc-interface of CCC: 2
      up (2), down (0)
      Interface                            Encap Type               State     VC Type
      GigabitEthernet0/3/0                 ethernet                 up        ccc
      GigabitEthernet0/3/2                 ethernet                 up        ccc
    • Run the display mpls l2vc remote-info command. The command output shows that Peer Addr is the peer address of the specified VC. For example:

      <HUAWEI> display mpls l2vc remote-info
      Total remote ldp vc : 1
      
      Transport  Group      Peer            Remote         Remote     C   MTU/  N   S
      VC ID      ID         Addr            Encap          VC Label   Bit CELLS Bit Bit
      100        0          192.168.3.3     vlan           18         0   1500  1   0
  • After VPLS is configured:

    Run the display vsi [ name vsi-name ] [ verbose ] command. The command output shows that the VSI State is Up. If you specify verbose, the command output shows that PW Signaling is LDP and that VSI State is Up. For example:

    <HUAWEI> display vsi name vsi1 verbose
     ***VSI Name               : ldp1
        Administrator VSI      : no
        Isolate Spoken         : disable
        VSI Index              : 1
        PW Signaling           : ldp
        Member Discovery Style : static
        Bridge-domain Mode     : disable
        PW MAC Learn Style     : unqualify
        Encapsulation Type     : vlan
        MTU                    : 1500
        Diffserv Mode          : uniform
        Service Class          : --
        Color                  : --
        DomainId               : 255
        Domain Name            :
        Ignore AcState         : disable
        P2P VSI                : disable
        Create Time            : 0 days, 0 hours, 3 minutes, 8 seconds
        VSI State              : up
    
        VSI ID                 : 2
       *Peer Router ID         : 2.2.2.9
        primary or secondary   : primary
        ignore-standby-state   : no
        VC Label               : 17
        Peer Type              : dynamic
        Session                : up
        Tunnel ID              :0x0000000001006a5c21
        Broadcast Tunnel ID    : --
        Broad BackupTunnel ID  : --
        CKey                   : 1
        NKey                   : 3154116711
        Stp Enable             : 0
        PwIndex                : 0
        Control Word           : disable
       *Peer Router ID         : 3.3.3.9
        primary or secondary   : primary
        ignore-standby-state   : no
        VC Label               : 18
        Peer Type              : dynamic
        Session                : up
        Tunnel ID              : 0x0000000001004c4b43
        Broadcast Tunnel ID    : --
        Broad BackupTunnel ID  : --
        CKey                   : 2
        NKey                   : 3154116712
        Stp Enable             : 0
        PwIndex                : 0
        Control Word           : disable
    
        Interface Name         : GigabitEthernet0/1/1.1
        State                  : up
        Access Port            : false
        Last Up Time           : 2012/07/19 03:19:14
        Total Up Time          : 0 days, 0 hours, 3 minutes, 11 seconds
    
      **PW Information:
    
       *Peer Ip Address        : 2.2.2.9
        PW State               : up
        Local VC Label         : 17
        Remote VC Label        : 17
        Remote Control Word    : disable
        PW Type                : label
        Tunnel ID              : 0x0000000001006a5c21
        Broadcast Tunnel ID    : --
        Broad BackupTunnel ID  : --
        Ckey                   : 1
        Nkey                   : 3154116711
        Main PW Token          : 0x0
        Slave PW Token         : 0x0
        Tnl Type               : ldp
        OutInterface           : LDP LSP
        Backup OutInterface    :
        Stp Enable             : 0
        PW Last Up Time        : 2012/07/19 03:21:09
        PW Total Up Time       : 0 days, 0 hours, 0 minutes, 29 seconds
       *Peer Ip Address        : 3.3.3.9
        PW State               : up
        Local VC Label         : 18
        Remote VC Label        : 17
        Remote Control Word    : disable
        PW Type                : label
        Tunnel ID              : 0x0000000001004c4b43
        Broadcast Tunnel ID    : --
        Broad BackupTunnel ID  : --
        Ckey                   : 2
        Nkey                   : 3154116712
        Main PW Token          : 0x0
        Slave PW Token         : 0x0
        Tnl Type               : ldp
        OutInterface           : LDP LSP
        Backup OutInterface    :
        Stp Enable             : 0
        PW Last Up Time        : 2012/07/19 03:21:09
        PW Total Up Time       : 0 days, 0 hours, 0 minutes, 29 seconds
  • After the L3VPN is configured:

    Run the display ip vpn-instance verbose [ vpn-instance-name ] command. The command output shows detailed information about each VPN instance, including the creation time, the amount of time the VPN instance remains in the Up state, the RD value, VPN target, and the policy used to assign the labels.

    <HUAWEI> display ip vpn-instance verbose
     Total VPN-Instances configured : 2
     Total IPv4 VPN-Instances configured : 2
     Total IPv6 VPN-Instances configured : 0
    
     VPN-Instance Name and ID : vpn1, 1
      Interfaces : GigabitEthernet0/1/1.1
     Address family ipv4
      Create date : 2012-07-18 14:34:48
      Up time : 0 days, 00 hours, 07 minutes and 54 seconds
      Vrf Status : UP
      Route Distinguisher : 100:1
      Export VPN Targets : 100:1
      Import VPN Targets : 100:1
      Label Policy : label per route
      The diffserv-mode Information is : uniform
      The ttl-mode Information is : pipe
    
     VPN-Instance Name and ID : vpn2, 2
      Interfaces : GigabitEthernet0/1/1.2
     Address family ipv4
      Create date : 2012-07-18 14:38:44
      Up time : 0 days, 00 hours, 03 minutes and 58 seconds
      Vrf Status : UP
      Route Distinguisher : 200:2
      Export VPN Targets : 200:2
      Import VPN Targets : 200:2
      Label Policy : label per route
      The diffserv-mode Information is : uniform
      The ttl-mode Information is : pipe

    Run the display bgp [ vpnv4 vpn-instance vpn-instance-name ] peer command. The command output shows that the BGP peer relationship has been established and is in the Established status.

    <HUAWEI> display bgp vpnv4 vpn-instance vpn1 peer
    BGP local router ID : 1.1.1.9
    Local AS number : 100
    
     VPN-Instance vpn1, router ID 1.1.1.9:
     Total number of peers : 1                 Peers in established state : 1
    
      Peer            V          AS    MsgRcvd  MsgSent  OutQ  Up/Down     State         PrefRcv
      10.1.1.2        4         65410     6        7       0 00:02:58      Established    1
Translation
Download
Updated: 2019-01-02

Document ID: EDOC1100055378

Views: 16772

Downloads: 35

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