ExOS VM and GNS3


Userlevel 2
Hello Guys,

I'm trying to set up a lab at the GNS3, so, i'm being able to configure the ExtremoXOS VM under GNS3, but when i set up a vpls between them, and connect a PC or any router under GNS3, i can't ping the host in other side. The questions is. Is it possible to integrate others device and make them speaking over vpls using GNS3?

P.S: When i configured only vlan tagged i can ping the PC's, when i start up the vpls and then is up, i can ping the host.

8 replies

Userlevel 6
welisson,

Could you post the following configuration and show outputs so I can get a better idea of your configuration:

show configuration ospf #or routing protocol in use
show configuration mpls
show configuration vlan [/code]show mpls ldp peer
show mpls rsvp-te neighbor
show mpls label
show l2vpn detail[/code]
Userlevel 2
Chad Smith wrote:

welisson,

Could you post the following configuration and show outputs so I can get a better idea of your configuration:

show configuration ospf #or routing protocol in use
show configuration mpls
show configuration vlan [/code]show mpls ldp peer
show mpls rsvp-te neighbor
show mpls label
show l2vpn detail[/code]

Hi Chad,

Here you go.

configure ospf routerid 1.1.1.1
enable ospf
configure ospf add vlan loopback0 area 0.0.0.0 passive
configure ospf add vlan sw01_sw03 area 0.0.0.0
configure ospf add vlan sw1_sw2 area 0.0.0.0

configure mpls add vlan "loopback0"
enable mpls vlan "loopback0"
enable mpls ldp vlan "loopback0"
configure mpls add vlan "sw01_sw03"
enable mpls vlan "sw01_sw03"
enable mpls ldp vlan "sw01_sw03"
configure mpls add vlan "sw1_sw2"
enable mpls vlan "sw1_sw2"
enable mpls ldp vlan "sw1_sw2"
configure mpls lsr-id 1.1.1.1
enable mpls protocol ldp
enable mpls
create l2vpn vpls vpls_cliente1 fec-id-type pseudo-wire 20
configure l2vpn vpls vpls_cliente1 add service vlan cliente1
create l2vpn vpls vpls_cliente2 fec-id-type pseudo-wire 25
configure l2vpn vpls vpls_cliente2 add service vlan cliente2
configure l2vpn vpls vpls_cliente1 add peer 3.3.3.3 core full-mesh
configure l2vpn vpls vpls_cliente2 add peer 3.3.3.3 core full-mesh

sh vlan
---------------------------------------------------------------------------------------------
Name VID Protocol Addr Flags Proto Ports Virtual
Active router
/Total
---------------------------------------------------------------------------------------------
cliente1 4091 12.12.12.2 /30 --L------------------V----- ANY 0 /0 VR-Default
cliente2 208 172.16.25.2 /24 ---------------------V----- ANY 1 /1 VR-Default
Default 1 ----------------------------------------------- ANY 0 /0 VR-Default
loopback0 4092 1.1.1.1 /32 -fL------o-----------l----- ANY 0 /0 VR-Default
Mgmt 4095 192.168.56.11 /24 --------------------------- ANY 0 /1 VR-Mgmt
sw01_sw03 4093 10.10.0.1 /30 -f-------o-----------l----- ANY 1 /1 VR-Default
sw1_sw2 4094 192.168.0.1 /30 -f-------o-----------l----- ANY 1 /1 VR-Default
---------------------------------------------------------------------------------------------
Flags : (B) BFD Enabled, (c) 802.1ad customer VLAN, (C) EAPS Control VLAN,
(d) Dynamically created VLAN, (D) VLAN Admin Disabled,
(e) CES Configured, (E) ESRP Enabled, (f) IP Forwarding Enabled,
(F) Learning Disabled, (i) ISIS Enabled, (I) Inter-Switch Connection VLAN for MLAG,
(k) PTP Configured, (l) MPLS Enabled, (L) Loopback Enabled,
(m) IPmc Forwarding Enabled, (M) Translation Member VLAN or Subscriber VLAN,
(n) IP Multinetting Enabled, (N) Network Login VLAN, (o) OSPF Enabled,
(O) Flooding Disabled, (p) PIM Enabled, (P) EAPS protected VLAN,
(r) RIP Enabled, (R) Sub-VLAN IP Range Configured,
(s) Sub-VLAN, (S) Super-VLAN, (t) Translation VLAN or Network VLAN,
(T) Member of STP Domain, (v) VRRP Enabled, (V) VPLS Enabled, (W) VPWS Enabled

Total number of VLAN(s) : 7

* SW01.4 # sh mpls ldp peer
IP Address LDP Peer State Uptime Adjacencies
1.1.1.1 3.3.3.3:0 Operational 0d:0h:37m:45s 2

* SW01.12 # show mpls label

Advertised Destination Label Peer NHop
Label Mapping Flags Label Type NextHop Name
-------------------------------------------------------------------------------
0x00074 1.1.1.1/32 -LE -- vlan loopback0 --
0x00076 3.3.3.3/32 2LE -- VPLS -- vpls_cliente2
0x00075 3.3.3.3/32 2LE -- VPLS -- vpls_cliente1


Received Destination Label
Label Mapping Flags NextHop Name
------------------------------------------------------------------------------
0x00076 3.3.3.3/32 2LI 3.3.3.3 vpls_cliente2
0x00074 3.3.3.3/32 -LI 10.10.0.2 --
0x00075 3.3.3.3/32 2LI 3.3.3.3 vpls_cliente1

Flags: (2) L2VPN, (L) LDP, (R) RSVP-TE, (S) Static,
(T) Transit LSP, (I) Ingress to LSP, (E) Egress from LSP,
(M) Multiple Next Hops

Summary of Labels Advertised Received
Total number of RSVP-TE LSP labels 0 0
Total number of LDP LSP labels 1 1
Total number of Static LSP labels 0 0
Total number of L2VPN labels 2 2

* SW01.13 # show mpls rsvp-te neighbor

show l2vpn detail
L2VPN Name: vpls_cliente1
VPN ID : 20 Admin State : Enabled
Source Address : 1.1.1.1 Oper State : Enabled
VCCV Status : Disabled MTU : 1500
VCCV Interval Time : 5 sec. Ethertype : 0x8100
VCCV Fault Multiplier : 4 .1q tag : exclude
L2VPN Type : VPLS Redundancy : None
Service Interface : cliente1

Peer IP: 3.3.3.3
PW State : Up
PW Uptime : 0d:0h:33m:38s
PW Installed : True
Local PW Status : No Faults
Remote PW Status : No Faults
Remote I/F MTU : 1500
PW Mode : Core-to-Core
Transport LSP : LDP LSP (Not Configured)
Next Hop I/F : sw01_sw03
Next Hop Addr : 10.10.0.2 Tx Label : 0x00074
PW Rx Label : 0x00075 PW Tx Label : 0x00075
PW Rx Pkts : n/a PW Tx Pkts : n/a
PW Rx Bytes : n/a PW Tx Bytes : n/a
MAC Limit : No Limit
VCCV HC Status : Not Sending (VCCV Not Enabled For This L2VPN)
CC Type : Rtr Alert Total Pkts Sent : 0
CV Type : LSP Ping Total Pkts Rcvd : 0
Send Next Pkt : --
Total Failures : 0 Pkts During Last Failure : 0
Last Failure Tm : --

L2VPN Name: vpls_cliente2
VPN ID : 25 Admin State : Enabled
Source Address : 1.1.1.1 Oper State : Enabled
VCCV Status : Disabled MTU : 1500
VCCV Interval Time : 5 sec. Ethertype : 0x8100
VCCV Fault Multiplier : 4 .1q tag : exclude
L2VPN Type : VPLS Redundancy : None
Service Interface : cliente2

Peer IP: 3.3.3.3
PW State : Up
PW Uptime : 0d:0h:40m:16s
PW Installed : True
Local PW Status : No Faults
Remote PW Status : No Faults
Remote I/F MTU : 1500
PW Mode : Core-to-Core
Transport LSP : LDP LSP (Not Configured)
Next Hop I/F : sw01_sw03
Next Hop Addr : 10.10.0.2 Tx Label : 0x00074
PW Rx Label : 0x00076 PW Tx Label : 0x00076
PW Rx Pkts : n/a PW Tx Pkts : n/a
PW Rx Bytes : n/a PW Tx Bytes : n/a
MAC Limit : No Limit
VCCV HC Status : Not Sending (VCCV Not Enabled For This L2VPN)
CC Type : Rtr Alert Total Pkts Sent : 0
CV Type : LSP Ping Total Pkts Rcvd : 0
Send Next Pkt : --
Total Failures : 0 Pkts During Last Failure : 0
Last Failure Tm : --

----------------------------------------

Total number of configured L2VPNs: 2
Total number of active L2VPNs: 2

Total number of configured PWs: 2
Total number of active PWs: 2
Total number of ready PWs: 0
PWs auto-selecting transport LSP: 2
PWs configured with a transport LSP: 0
PWs using LDP for transport: 2
PWs using RSVP for transport: 0
PWs using static for transport: 0

* SW01.15 # sh version
Switch : PN:1N2039 SN:123456 Rev 0.1 BootROM: 1.2 IMG: 15.2.1.5
PSUCTRL-1 : PN:MEAD SN:MD1 Rev 0.1 BootROM: 2.1
PSUCTRL-2 : PN:MEAD SN:MD2 Rev 1.1 BootROM: 2.3
mouse-usb : PN:MOUSE SN:4321 Rev 1.1 BootROM: 4.3
floppy-A :
PSU-1 : Stack PS Slot # 2 PN:1N2039 SN:1234 Rev 0.1
PSU-2 : Stack PS Slot # 3 PN:1N2039 SN:1234 Rev 0.1

Image : ExtremeXOS version 15.2.1.5 v1521b5 by release-manager
on Fri Aug 17 16:24:45 EDT 2012
Welisson what current code is running on the emulators I believe there is 2 versions out there one running 15.3 code i think and the other an older version of code, there is limited functionality you will get out of those VM....
Userlevel 6
Welisson,

EXOS-VM does not support VPLS.

That functionality requires hardware support and is not implemented in the VM...
Userlevel 2
dflouret wrote:

Welisson,

EXOS-VM does not support VPLS.

That functionality requires hardware support and is not implemented in the VM...

Hi Daniel Flouret,

So, this case i can set up the vpls and configured ip under vlan over vpls, in this case i was able ping each side, but when i put one host in both side, i can't ping each other, i'm able ping just next-hop, in case will be my PE.

sh vpls vpls_cliente2
L2VPN Name VPN ID Flags Services Name Peer IP State Flags
--------------- ------ ------- --------------- --------------- ----- ------
vpls_cliente2 25 EAX--L- cliente2 3.3.3.3 Up C---V-

L2VPN Name: vpls_cliente2
VPN ID : 25 Admin State : Enabled
Source Address : 1.1.1.1 Oper State : Enabled
VCCV Status : Disabled MTU : 1500
VCCV Interval Time : 5 sec. Ethertype : 0x8100
VCCV Fault Multiplier : 4 .1q tag : exclude
L2VPN Type : VPLS Redundancy : None
Service Interface : cliente2

Peer IP: 3.3.3.3
PW State : Up
PW Uptime : 0d:0h:46m:41s
PW Installed : True
Remote PW Status : No Faults
Remote I/F MTU : 1500
PW Mode : Core-to-Core
Transport LSP : LDP LSP (Not Configured)
Next Hop I/F : sw01_sw03
Next Hop Addr : 10.10.0.2 Tx Label : 0x00074
PW Rx Label : 0x00076 PW Tx Label : 0x00076
PW Rx Pkts : n/a PW Tx Pkts : n/a
PW Rx Bytes : n/a PW Tx Bytes : n/a
MAC Limit : No Limit
VCCV HC Status : Not Sending (VCCV Not Enabled For This L2VPN)
CC Type : Rtr Alert Total Pkts Sent : 0
CV Type : LSP Ping Total Pkts Rcvd : 0
Send Next Pkt : --
Total Failures : 0 Pkts During Last Failure : 0
Last Failure Tm : --

in this log i can see the vpls up in both side.
Userlevel 6
dflouret wrote:

Welisson,

EXOS-VM does not support VPLS.

That functionality requires hardware support and is not implemented in the VM...

welisson,

Notice the "PW Rx Pkts" "PW Tx Pkts" fields in the "show l2vpn detail" output. If the pseudo wire was fully up and operational, data would be exchanged and "n/a" would be replaced with a number.

Daniel is correct. The L2VPN pseudo wire is implemented in hardware and this functionality is not available in the EXOS VM.

You can configure MPLS, LDP (or RSVP-TE), and even setup the L2VPN service, but actual traffic will not pass across the VPN due to the lack of hardware support.
Userlevel 2
dflouret wrote:

Welisson,

EXOS-VM does not support VPLS.

That functionality requires hardware support and is not implemented in the VM...

Now is clear to me.

Therefore, if i need test the vpls with traffic pass across the cloud mpls, i need to buy a switch once it there is this feature based in hardware.

Chad Is there any possibility this be implemented in EXOS VM as way lab?

Tks
Welisson
Userlevel 6
dflouret wrote:

Welisson,

EXOS-VM does not support VPLS.

That functionality requires hardware support and is not implemented in the VM...

Unfortunately, there are currently no plans to implement this in EXOS VM

Reply