Read, Simon | 23 Apr 09:59 2014

Additional remediation of new P2P applications in NAC

Hi All,

 

Anybody know if it’s possible to add additional P2P applications to NAC. We have had success in our PoC with Limewire and utorrent, but not with Vuze and Mediaget.

 

 

Any suggestions would be appreciated.

 

Simon Read

Network Specialist

 

Nashua Communications (Pty) Ltd.

Unit 12 Growthpoint Business Park,

No 2 Tonnetti Street, Midrand, 1685

Cell: +27 (0)84  676 9200

DDI:+27 (0)10 001 3042

Fax: +27  (0)10 001 2500

simon.read <at> nashua-communications.com

www.nashua-communications.com

 

 

From: John Kaftan [mailto:jkaftan <at> utica.edu]
Sent: 22 April 2014 05:47 PM
To: Enterasys Customer Mailing List
Subject: Re: [enterasys] N7: Netflow Interface names?

 

Thank you I will try that.

On Apr 22, 2014 11:18 AM, <djohnson <at> fhsu.edu> wrote:

I've done this by adding the following string:

Alias: $alarmSubcomponent

Derek Johnson | Data Communications Coordinator
FORT HAYS STATE UNIVERSITY
415 Lyman Dr. TH 101, Hays, KS 67601

(785) 628 - 5688 | djohnson <at> fhsu.edu





From:        John Kaftan <jkaftan <at> utica.edu>
To:        "Enterasys Customer Mailing List" <enterasys <at> listserv.unc.edu>
Date:        04/22/2014 08:24 AM
Subject:        Re: [enterasys] N7: Netflow Interface names?




I am looking for a way to include interface names with alerts.  When I get an alert from an interface going down on an S4 I would like the port alias included so I know what it is.  So far I have added the $alarmSubcomponent to the body of my alert but that hasn't worked.  Does anyone have this working?

Thanks

Device: $deviceIp
Severity: $severity
Message: $message
Other Info: $alarmSubcomponent


On Tue, Apr 22, 2014 at 4:27 AM, Matthias Nees <M.Nees <at> bell.de> wrote:
Hi,

in recent N7 Firmware you can set this with:

set netflow export-data enable mac or  vlan


Regards,
Matthias Nees

-----Ursprüngliche Nachricht-----
Von: Stefan Hofem [mailto:stefan.hofem <at> ludwigshafen.de]
Gesendet: Dienstag, 22. April 2014 09:32
An: Enterasys Customer Mailing List
Betreff: [enterasys] N7: Netflow Interface names?

Hi,

is there an option similar to the Cisco "ip flow-export interface-names" command to add the interface-names to the flows?

Netflow-exporter is an old N7 (07.41.03)?

Regards
Stefan Hofem
---
To unsubscribe from enterasys, send email to listserv <at> unc.edu with the body: unsubscribe enterasys M.Nees <at> bell.de



--
John Kaftan
IT Infrastructure Manager
Utica College



Disclaimer and Confidentiality Note: This e-mail communication, its attachments, if any, and any rights attaching to it are, unless the context clearly indicates otherwise, the property of Nashua Communications. It is confidential, private and intended for the addressee only. If you are not the intended recipient and receive this communication in error, you are hereby notified that any review, copying, use, discloser or distribution in any manner whatsoever is strictly prohibited. Please notify the sender immediately that you have received this e-mail in error and delete the e-mail and any copies of it. Views and opinions expressed in this e-mail are those of the sender unless clearly stated as those of Nashua Communications. Nashua Communications accepts no liability for any loss or damage whatsoever, and howsoever incurred or suffered resulting or arising from the use of this e-mail communication and/or its attachments. Nashua Communications does not warrant the integrity of this e-mail communication nor that it is free of errors, viruses, interception or interference. Nashua Communications, its divisions and subsidiary companies expressly excludes sections 11, 12, and 13 of the Electronic Communications and Transactions Act, 25 of 2002 (“the ECT”) in respect of e-contracting. No data message or electronic communication will be recognised as having a legal contractual status under the ECT Act. All agreements concluded by Nashua Communications will only be legally binding when reduced to physical writing and physically signed by a duly authorised representative of Nashua Communications. For more information about Nashua Communications, visit our website at www.nashuacommunications.co.za

  • --To unsubscribe from enterasys, send email to listserv <at> unc.edu with the body: unsubscribe enterasys gneu-enterasys <at> gmane.org
John Kaftan | 22 Apr 17:46 2014

Re: N7: Netflow Interface names?

Thank you I will try that.

On Apr 22, 2014 11:18 AM, <djohnson <at> fhsu.edu> wrote:
I've done this by adding the following string:

Alias: $alarmSubcomponent

Derek Johnson | Data Communications Coordinator
FORT HAYS STATE UNIVERSITY
415 Lyman Dr. TH 101, Hays, KS 67601
(785) 628 - 5688 | djohnson <at> fhsu.edu





From:        John Kaftan <jkaftan <at> utica.edu>
To:        "Enterasys Customer Mailing List" <enterasys <at> listserv.unc.edu>
Date:        04/22/2014 08:24 AM
Subject:        Re: [enterasys] N7: Netflow Interface names?



I am looking for a way to include interface names with alerts.  When I get an alert from an interface going down on an S4 I would like the port alias included so I know what it is.  So far I have added the $alarmSubcomponent to the body of my alert but that hasn't worked.  Does anyone have this working?

Thanks

Device: $deviceIp
Severity: $severity
Message: $message
Other Info: $alarmSubcomponent


On Tue, Apr 22, 2014 at 4:27 AM, Matthias Nees <M.Nees <at> bell.de> wrote:
Hi,

in recent N7 Firmware you can set this with:

set netflow export-data enable mac or  vlan


Regards,
Matthias Nees

-----Ursprüngliche Nachricht-----
Von: Stefan Hofem [mailto:stefan.hofem <at> ludwigshafen.de]
Gesendet: Dienstag, 22. April 2014 09:32
An: Enterasys Customer Mailing List
Betreff: [enterasys] N7: Netflow Interface names?

Hi,

is there an option similar to the Cisco "ip flow-export interface-names" command to add the interface-names to the flows?

Netflow-exporter is an old N7 (07.41.03)?

Regards
Stefan Hofem
---
To unsubscribe from enterasys, send email to listserv <at> unc.edu with the body: unsubscribe enterasys M.Nees <at> bell.de



--
John Kaftan
IT Infrastructure Manager
Utica College

  • --To unsubscribe from enterasys, send email to listserv <at> unc.edu with the body: unsubscribe enterasys gneu-enterasys <at> gmane.org
djohnson | 22 Apr 17:18 2014

Re: N7: Netflow Interface names?

I've done this by adding the following string:

Alias: $alarmSubcomponent

Derek Johnson | Data Communications Coordinator
FORT HAYS STATE UNIVERSITY
415 Lyman Dr. TH 101, Hays, KS 67601
(785) 628 - 5688 | djohnson <at> fhsu.edu





From:        John Kaftan <jkaftan <at> utica.edu>
To:        "Enterasys Customer Mailing List" <enterasys <at> listserv.unc.edu>
Date:        04/22/2014 08:24 AM
Subject:        Re: [enterasys] N7: Netflow Interface names?



I am looking for a way to include interface names with alerts.  When I get an alert from an interface going down on an S4 I would like the port alias included so I know what it is.  So far I have added the $alarmSubcomponent to the body of my alert but that hasn't worked.  Does anyone have this working?

Thanks

Device: $deviceIp
Severity: $severity
Message: $message
Other Info: $alarmSubcomponent


On Tue, Apr 22, 2014 at 4:27 AM, Matthias Nees <M.Nees <at> bell.de> wrote:
Hi,

in recent N7 Firmware you can set this with:

set netflow export-data enable mac or  vlan


Regards,
Matthias Nees

-----Ursprüngliche Nachricht-----
Von: Stefan Hofem [mailto:stefan.hofem <at> ludwigshafen.de]
Gesendet: Dienstag, 22. April 2014 09:32
An: Enterasys Customer Mailing List
Betreff: [enterasys] N7: Netflow Interface names?

Hi,

is there an option similar to the Cisco "ip flow-export interface-names" command to add the interface-names to the flows?

Netflow-exporter is an old N7 (07.41.03)?

Regards
Stefan Hofem
---
To unsubscribe from enterasys, send email to listserv <at> unc.edu with the body: unsubscribe enterasys M.Nees <at> bell.de



--
John Kaftan
IT Infrastructure Manager
Utica College
  • --To unsubscribe from enterasys, send email to listserv <at> unc.edu with the body: unsubscribe enterasys djohnson <at> fhsu.edu

  • --To unsubscribe from enterasys, send email to listserv <at> unc.edu with the body: unsubscribe enterasys gneu-enterasys <at> gmane.org
John Kaftan | 22 Apr 15:24 2014

Re: N7: Netflow Interface names?

I am looking for a way to include interface names with alerts.  When I get an alert from an interface going down on an S4 I would like the port alias included so I know what it is.  So far I have added the $alarmSubcomponent to the body of my alert but that hasn't worked.  Does anyone have this working?

Thanks

Device: $deviceIp
Severity: $severity
Message: $message
Other Info: $alarmSubcomponent


On Tue, Apr 22, 2014 at 4:27 AM, Matthias Nees <M.Nees <at> bell.de> wrote:
Hi,

in recent N7 Firmware you can set this with:

set netflow export-data enable mac or  vlan


Regards,
Matthias Nees

-----Ursprüngliche Nachricht-----
Von: Stefan Hofem [mailto:stefan.hofem <at> ludwigshafen.de]
Gesendet: Dienstag, 22. April 2014 09:32
An: Enterasys Customer Mailing List
Betreff: [enterasys] N7: Netflow Interface names?

Hi,

is there an option similar to the Cisco "ip flow-export interface-names" command to add the interface-names to the flows?

Netflow-exporter is an old N7 (07.41.03)?

Regards
Stefan Hofem
---
To unsubscribe from enterasys, send email to listserv <at> unc.edu with the body: unsubscribe enterasys M.Nees <at> bell.de



--
John Kaftan
IT Infrastructure Manager
Utica College

  • --To unsubscribe from enterasys, send email to listserv <at> unc.edu with the body: unsubscribe enterasys gneu-enterasys <at> gmane.org
Matthias Nees | 22 Apr 10:27 2014
Picon

AW: N7: Netflow Interface names?

Hi,

in recent N7 Firmware you can set this with:

set netflow export-data enable mac or  vlan


Regards,
Matthias Nees

-----Ursprüngliche Nachricht-----
Von: Stefan Hofem [mailto:stefan.hofem <at> ludwigshafen.de] 
Gesendet: Dienstag, 22. April 2014 09:32
An: Enterasys Customer Mailing List
Betreff: [enterasys] N7: Netflow Interface names?

Hi,

is there an option similar to the Cisco "ip flow-export interface-names" command to add the
interface-names to the flows? 

Netflow-exporter is an old N7 (07.41.03)?

Regards
Stefan Hofem
---
To unsubscribe from enterasys, send email to listserv <at> unc.edu with the body: unsubscribe enterasys M.Nees <at> bell.de
Attachment (smime.p7s): application/x-pkcs7-signature, 2779 bytes
Stefan Hofem | 22 Apr 09:31 2014
Picon

N7: Netflow Interface names?

Hi,

is there an option similar to the Cisco "ip flow-export interface-names" command to add the
interface-names to the flows? 

Netflow-exporter is an old N7 (07.41.03)?

Regards
Stefan Hofem
---
To unsubscribe from enterasys, send email to listserv <at> unc.edu with the body: unsubscribe enterasys gneu-enterasys <at> gmane.org

John Kaftan | 17 Apr 19:28 2014

Fwd: Conference!!!


Hello:

On behalf of the Extreme Upstate Users Group (EUUG), in upstate New York,  I am happy to announced our 3rd conference to be held on June 11th, at Nazareth College in Rochester NY, and now also by web-cast.

The conferences prior have focused on Policy and NAC and data center technologies.  For this conferences we are going deep with Netsight.  We figure it is time to get to the foundation to help fully leverage this powerful network management tool.

Please see the attached agenda for details on the day.  After the conference we plan to take in the Rochester night life so we hope you can stay and socialize.  We have negotiated a group rate at a nearby hotel and are working on transportation for the day.

We hope you can make it.  These conferences are informative and help us build our professional networks.  However, if you cannot make it physically please join us virtually via web-cast.  Whether joining us in person or virtually, just register here and we will provide you with all of the details.

Thank you


--
John Kaftan
IT Infrastructure Manager
Utica College

  • --To unsubscribe from enterasys, send email to listserv <at> unc.edu with the body: unsubscribe enterasys gneu-enterasys <at> gmane.org
Erik Auerswald | 17 Apr 13:51 2014
Picon

Re: Fwd: LACP lag issue between switches and clients on same subnet.

Hi,

the LAG obviously forms and the fact that routed connections use different
physical links shows that L3 information is used for hashing, not just L2.
Unless per frame round-robin is used, any combination of client and server
will always use the same physical link. Both directions use the same link.

My interpretation is that your test clients in the same subnet by chance
use the same link. To verify change the IP address of one of the clients
to get it to use the other physical link.

On an S-Series with current firmware you can use 'show lacp
outputportAlgorithm' to verify that the default of L3 (dip-sip) is used.
You can even change it with 'set lacp outportAlgorithm', but it do not
recommend this.

With a significant number of clients all links of the LAG will be used.

HTH,
Erik
-- 
Dipl.-Inform. Erik Auerswald         http://www.fg-networking.de/
auerswald <at> fg-networking.de T:+49-631-4149988-0 M:+49-176-64228513

Gesellschaft für Fundamental Generic Networking mbH
Geschäftsführung: Volker Bauer, Jörg Mayer
Gerichtsstand: Amtsgericht Kaiserslautern - HRB: 3630

On Thu, Apr 17, 2014 at 12:19:35PM +0100, Charlie Daffarn wrote:
> hi all,
> 
> We have a new Windows 2012 R2 files server which will require maximum speed
> comms between them and the users. Windows 2012 now allows, natively, for a
> 2+ nic team, using a dynamic LACP lag to the switch.
> 
> The server is in a specific vlan (1010), with the 2 x nic ports, and the
> lag in that vlan, untagged.  All client desktops are in different vlans,
> based on their physical location (eg floor).
> 
> Once configured on the server,  the switch config shows:
> 
> #show lacp
> 
> Aggregator:  lag.0.12
>                           Actor                 Partner
> System Identifier:  00:01:f4:7e:89:bf      d8:9d:67:79:12:94
>   System Priority:              32768                      0
>         Admin Key:              32768
>          Oper Key:              32768                      0
>    Attached Ports:  ge.2.18-19
> 
> #show config vlan
> 
> *set vlan egress 1010
> lag.0.12*;ge.1.1-7,26,29*;ge.2*.1-7,*18-19*,36;ge.3.1-7,17,19
> *untagged*
> 
> #show port vlan ge.2.18-19;lag.0.12
> ge.2.18 is set to 1010
> ge.2.19 is set to 1010
> lag.0.12 is set to 1010
> 
> #show port status ge.2.18-19;lag.0.12
> Port         Alias            Oper     Admin   Speed  Duplex  Type
>              (truncated)      Status   Status  (bps)
> ------------ ---------------- -------- ------- ------ -------
> ------------------
> ge.2.18                       dormant  up        1.0G full    1000-t
> rj45
> ge.2.19                       dormant  up        1.0G full    1000-t
> rj45
> lag.0.12                      up       up        2.0G         lag
> 3 of 3 ports displayed, 3 port(s) with oper status 'up' or 'dormant'.
> 
> 
> Test copying a file to or from a client and the server on one particular
> subnet, and another client on a different subnet, either on the same edge
> switch, or a different switch, to the server, allows each client to each
> use one of the connected nics, to achieve > 2gbps transfer speed.
> 
> If we copy from 2 clients, on the same subnet, the copy drops to half speed
> on both client, ie, they both use the same connected nic. This behaviour
> occurs copying to, or from the server.
> 
> In theory, the subnet the clients are on shouldn't affect the load balanced
> lag, but it seems this is not the case.
> 
> The windows lacp config allows either a Dynamic Load Balanced Mode, or
> Address Hash mode. We've tried both....both form the dynamic lag on the
> switch, with the same copy speed results.
> 
> Is there any reason, from a network pov, you can think of why we're seeing
> this behaviour...have you seen this before, and do you have any ideas on
> how we can resolve it, save from having each user/client in it's own
> subnet/vlan, which would lead to it's own, more significant admin related
> problems!!
> 
> thanks all,
> Charlie.
> 
> -- 
> This e-mail is intended only for the named person or entity to which it is addressed and
> contains valuable business information that is proprietary, privileged, confidential and/or
> otherwise protected from disclosure. If you received this e-mail in error, any review, use,
> dissemination, distribution or copying of this e-mail is strictly prohibited. Please notify
> us immediately of the error via e-mail to wrong.recipient <at> uk-group.net and please delete
> the e-mail from your system, retaining no copies in any media. We appreciate your cooperation.
> 
> ---
> To unsubscribe from enterasys, send email to listserv <at> unc.edu with the body: unsubscribe enterasys auerswald <at> fg-networking.de

---
To unsubscribe from enterasys, send email to listserv <at> unc.edu with the body: unsubscribe enterasys gneu-enterasys <at> gmane.org

enterasys@listserv.unc.edu | 17 Apr 13:20 2014

Fwd: LACP lag issue between switches and clients on same subnet.

Hola buen día, 

Estaré fuera de la oficina del Lunes 7 al viernes 18 de abril, tendré  acceso limitado a mis correos de voz y
electrónicos  por lo que demorare en mi respuesta.
Si tu asunto requiere atención inmediata, por favor comunicarse con David Aguilar al teléfono 9000
1777, al celular 55 5217 3678 o al correo david.aguilar <at> netcontroll.com.

Saludos,
Gracias.

---
To unsubscribe from enterasys, send email to listserv <at> unc.edu with the body: unsubscribe enterasys gneu-enterasys <at> gmane.org

Charlie Daffarn | 17 Apr 13:19 2014

Fwd: LACP lag issue between switches and clients on same subnet.

hi all,

We have a new Windows 2012 R2 files server which will require maximum speed comms between them and the users. Windows 2012 now allows, natively, for a 2+ nic team, using a dynamic LACP lag to the switch.

The server is in a specific vlan (1010), with the 2 x nic ports, and the lag in that vlan, untagged.  All client desktops are in different vlans, based on their physical location (eg floor).

Once configured on the server,  the switch config shows:

#show lacp

Aggregator:  lag.0.12
                          Actor                 Partner
System Identifier:  00:01:f4:7e:89:bf      d8:9d:67:79:12:94
  System Priority:              32768                      0
        Admin Key:              32768
         Oper Key:              32768                      0
   Attached Ports:  ge.2.18-19

#show config vlan

set vlan egress 1010 lag.0.12;ge.1.1-7,26,29;ge.2.1-7,18-19,36;ge.3.1-7,17,19 untagged

#show port vlan ge.2.18-19;lag.0.12
ge.2.18 is set to 1010
ge.2.19 is set to 1010
lag.0.12 is set to 1010

#show port status ge.2.18-19;lag.0.12
Port         Alias            Oper     Admin   Speed  Duplex  Type
             (truncated)      Status   Status  (bps)
------------ ---------------- -------- ------- ------ ------- ------------------
ge.2.18                       dormant  up        1.0G full    1000-t       rj45
ge.2.19                       dormant  up        1.0G full    1000-t       rj45
lag.0.12                      up       up        2.0G         lag
3 of 3 ports displayed, 3 port(s) with oper status 'up' or 'dormant'.


Test copying a file to or from a client and the server on one particular subnet, and another client on a different subnet, either on the same edge switch, or a different switch, to the server, allows each client to each use one of the connected nics, to achieve > 2gbps transfer speed.

If we copy from 2 clients, on the same subnet, the copy drops to half speed on both client, ie, they both use the same connected nic. This behaviour occurs copying to, or from the server.

In theory, the subnet the clients are on shouldn't affect the load balanced lag, but it seems this is not the case.

The windows lacp config allows either a Dynamic Load Balanced Mode, or Address Hash mode. We've tried both....both form the dynamic lag on the switch, with the same copy speed results.

Is there any reason, from a network pov, you can think of why we're seeing this behaviour...have you seen this before, and do you have any ideas on how we can resolve it, save from having each user/client in it's own subnet/vlan, which would lead to it's own, more significant admin related problems!!

thanks all,
Charlie.
-- -- This e-mail is intended only for the named person or entity to which it is addressed and contains valuable business information that is proprietary, privileged, confidential and/or otherwise protected from disclosure. If you received this e-mail in error, any review, use, dissemination, distribution or copying of this e-mail is strictly prohibited. Please notify us immediately of the error via e-mail to wrong.recipient <at> uk-group.net and please delete the e-mail from your system, retaining no copies in any media. We appreciate your cooperation.

  • --To unsubscribe from enterasys, send email to listserv <at> unc.edu with the body: unsubscribe enterasys gneu-enterasys <at> gmane.org
Mamabolo, Pheko | 10 Apr 15:24 2014
Picon

RE: OpenSSL Heartbleed Vulnerability Query

Hi Derek,

 

Thank you, also see below.

 

https://community.extremenetworks.com/extreme/topics/heartbleed_openssl_vulnerability_in_nms_oneview_or_wireless_controller

 

Netsite 5.0.0.231
SIEM 7.7.2 Patch 1 (Build 614901 (7.2.0.614901))
use libssl.so.1.0.0. 


NAC Gateway 5.0.0.231
uses libssl.so 0.9.8

So it looks like those versions are not vulnerable.

 

 

From: djohnson <at> fhsu.edu [mailto:djohnson <at> fhsu.edu]
Sent: 10 April 2014 14:59
To: Enterasys Customer Mailing List
Subject: Re: [enterasys] OpenSSL Heartbleed Vulnerability Query

 

I'm still running 08.32.01.0035 and can confirm it is not vulnerable.

If you have Internet access to the box, you can safely test yours using http://filippo.io/Heartbleed/

 

To test my systems internally, I used the modified python script linked within the article below:



Derek Johnson
Data Communications Coordinator
Fort Hays State University
(785) 628 - 5688
djohnson <at> fhsu.edu



-----"Mamabolo, Pheko" <pheko.mamabolo <at> siemens.com> wrote: -----

To: "Enterasys Customer Mailing List" <enterasys <at> listserv.unc.edu>
From: "Mamabolo, Pheko" <pheko.mamabolo <at> siemens.com>
Date: 04/10/2014 05:34AM
Subject: [enterasys] OpenSSL Heartbleed Vulnerability Query

Hi

 

Does anyone know if Enterasys WLAN Controller that is running version 08.11.02.0023 could be running OpenSSL from 1.0.1 through 1.0.1f (i.e. inclusive) whether  this has the Heartbleed vulnerability?

 

With best regards,

Pheko Mamabolo

 

 

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

Disclaimer and

Confidentiality Note

 

This e-mail

communication, its attachments, if any, and any rights attaching to it are,

unless the context clearly indicates otherwise, the property of Siemens (Pty)

Ltd. It is confidential, private and intended for the addressee only. If you are

not the intended recipient and receive this communication in error, you are

hereby notified that any review, copying, use, discloser or distribution in any

manner whatsoever is strictly prohibited. Please notify the sender immediately

that you have received this e-mail in error and delete the e-mail and any copies

of it. Views and opinions expressed in this e-mail are those of the sender

unless clearly stated as those of Siemens (Pty) Ltd. Siemens (Pty) Ltd accepts

no liability for any loss or damage whatsoever, and howsoever incurred or

suffered resulting or arising from the use of this e-mail communication and/or

its attachments.

 

Siemens (Pty)

Ltd does not warrant the integrity of this e-mail communication nor that it is

free of errors, viruses, interception or interference.

 

Siemens (Pty)

Ltd, its divisions and subsidiary companies (“Siemens”) expressly excludes

sections 11, 12, and 13 of the Electronic Communications and Transactions Act,

25 of 2002 (“the ECT”) in respect of e-contracting.  No data message or

electronic communication will be recognised as having a legal contractual status

under the ECT Act.  All agreements concluded by Siemens will only be

legally binding when reduced to physical writing and physically signed by a duly

authorised representative of Siemens.

 

For more

information about Siemens (Pty) Ltd, visit our website at www.siemens.com

 

 

 

Siemens

(Proprietary) Limited

 

Company

Registration Number: 1923/007514/07

 

Registered

Address: 300 Janadel Avenue, Halfway House, 1685

 

VAT

Registration Number: 4790104428

 

Chairman: Prof

Dr S Russwurm *

 

Chief

Executive Officer: SG Proebstl * ; Chief Financial Officer: SU Dall’Omo

*

 

Executive

Directors: C Klaas; R Nkuhlu

 

Non-Executive

Directors: R Guntermann *; Dr MI Survé

 

Alternate

Directors: I Amod; Dr H Grundmann *

 

Company

Secretary: T Llale

 

                                                     

* German


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

 

  • --To unsubscribe from enterasys, send email to listserv <at> unc.edu with the body: unsubscribe enterasys gneu-enterasys <at> gmane.org

Gmane