Ooo. Eval code might do the trick since this really is for testing.
Thanks guys!
Jay
From: Yang, Charles [mailto:***@massport.com]
Sent: Thursday, November 21, 2013 4:01 PM
To: Enterasys Customer Mailing List
Subject: RE: [enterasys] Remote Mirroring using a Layer 2 GRE Tunnel on S-series
Yap. It needs 1)v8 code 2) advance license.
You can also request an eval code for testing.
-cy
From: Markus Kaiser [mailto:***@enterasys.com]
Sent: Thursday, November 21, 2013 3:50 PM
To: Enterasys Customer Mailing List
Subject: Re: [enterasys] Remote Mirroring using a Layer 2 GRE Tunnel on S-series
Hi,
you have S150 modules and there's a
optional License S-EOS-L3-S150 which
enables (L3) GRE Tunneling.
For S130 it says in general "Tunneling" for the Advanced L3 License.
I will need to verify this again with my colleagues.
You might also need a 8.x code on both devices.
Maybe someone else can answer this for sure, but will clarify this tomorrow.
Kind regards,
Markus
___________________________
On 21.11.2013, at 20:52, "Auger, Jay (IS)" <***@umassmed.edu<mailto:***@umassmed.edu>> wrote:
Mirror source port is on an S4 (2x SK1208-0808-F6 & SK1008-0816) running 08.11.04.0005, target would be on an S4 (2x SK1208-0808-F6) running 07.73.01.0003.
When I run 'show licenses' I get: 'There are no licenses configured.'
Thx!
Jay
From: Markus Kaiser [mailto:***@enterasys.com]
Sent: Thursday, November 21, 2013 2:44 PM
To: Enterasys Customer Mailing List
Subject: Re: [enterasys] Remote Mirroring using a Layer 2 GRE Tunnel on S-series
Hi,
Which type of S-Series or modules?
It's maybe a license issue.
Do you run version 7 or 8 code?
Kind regards,
Markus
___________________________
On 21.11.2013, at 20:37, "Auger, Jay (IS)" <***@umassmed.edu<mailto:***@umassmed.edu>> wrote:
Hi all,
Has anyone successfully implemented a remote mirror on S-series? I found the document on the Enterasys extranet that describes this as well as configuration examples but I can't seem to run the command 'interface tunnel x'. The option doesn't exist.
Much appreciated,
Jay
* --To unsubscribe from enterasys, send email to ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@enterasys.com<mailto:***@enterasys.com>
* --To unsubscribe from enterasys, send email to ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@umassmed.edu<mailto:***@umassmed.edu>
* --To unsubscribe from enterasys, send email to ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@enterasys.com<mailto:***@enterasys.com>
* --To unsubscribe from enterasys, send email to ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@massport.com<mailto:***@massport.com>
* --To unsubscribe from enterasys, send email to ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@umassmed.edu<mailto:***@umassmed.edu>
---
To unsubscribe from enterasys, send email to ***@unc.edu with the body: unsubscribe enterasys gneu-***@gmane.org