Discussion:
- Enterasys Wireless Controller intergration with Enterasys NAC - SNMP error
Read, Simon
2013-05-02 10:02:53 UTC
Permalink
Hi All,

Would very much appreciate any feedback or suggestions on the following. I have a C25 and LPA successfully managed in NetSight via SNMPv3. What I am trying to do is create a single NAC VNS that allows access for Authenticated and Unauthenticated, (Guest) devices.

802.1x authenticated users connect to the VNS and can be remediated, no problem.

Unauthenticated users should connect to the VNS and then find themselves directed to NAC's login page when they open a browser. I am seeing in NAC that the connection attempt is, "Accept", but MAC-to-IP Address resolution fails. There are ip helper-addresses on the relevant Core switches VLAN GW that point to the DHCP server, the Layer-3 interface created for the NAC VNS and even the management IP address of the Controller.

I've set debugging for DHCP, IP resolution and SNMP to Verbose and in the tag.log and I am seeing the following error...

DEBUG [SnmpManager] Unable to get SnmpSwitch for IP: 127.0.0.1 sw: null

Has anybody seen this error before and/ or are there any suggestions on what might be causing it?


Kind regards,

Simon Read
Service Engineer


[Nashua Communications EMAIL Logo2.gif]


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 ***@unc.edu with the body: unsubscribe enterasys gneu-***@gmane.org
Kurtman, Emre
2013-05-02 14:04:32 UTC
Permalink
Hi Simon,

You should also add an ip helper address pointing to NAC's ip address so
that NAC can resolve the IP address of the client.

Thanks,
Emre


On Thu, May 2, 2013 at 1:02 PM, Read, Simon <
Hi All,****
** **
Would very much appreciate any feedback or suggestions on the following. I
have a C25 and LPA successfully managed in NetSight via SNMPv3. What I am
trying to do is create a single NAC VNS that allows access for
Authenticated and Unauthenticated, (Guest) devices.****
** **
802.1x authenticated users connect to the VNS and can be remediated, no
problem.****
** **
Unauthenticated users should connect to the VNS and then find themselves
directed to NAC’s login page when they open a browser. I am seeing in NAC
that the connection attempt is, “Accept”, but MAC-to-IP Address resolution
fails. There are ip helper-addresses on the relevant Core switches VLAN GW
that point to the DHCP server, the Layer-3 interface created for the NAC
VNS and even the management IP address of the Controller.****
** **
I’ve set debugging for DHCP, IP resolution and SNMP to Verbose and in the
tag.log and I am seeing the following error… ****
** **
DEBUG [SnmpManager] Unable to get SnmpSwitch for IP: 127.0.0.1 sw: null***
*
** **
Has anybody seen this error before and/ or are there any suggestions on
what might be causing it?****
** **
* *
Kind regards, ****
* *
*Simon Read*
*Service Engineer***
** **
** **
[image: Nashua Communications EMAIL Logo2.gif]****
** **
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
--
Emre Kurtman
Enterasys Networks
Cell: +90533 3302766
Email: ***@enterasys.com

*There is nothing more important than our customers.*
**

---
To unsubscribe from enterasys, send email to ***@unc.edu with the body: unsubscribe enterasys gneu-***@gmane.org
Read, Simon
2013-05-03 07:08:03 UTC
Permalink
Hi Emre,

Thanks. There is also the ip address of NAC included. Sorry I missed it before.


Kind regards,

Simon Read
Service Engineer

Nashua Communications (Pty) Ltd.
Unit 10 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
***@nashua-communications.com<mailto:***@nashua-communications.com>
www.nashua-communications.com<http://www.nashua-communications.com/>

[Nashua Communications EMAIL Logo2.gif]

From: Kurtman, Emre [mailto:***@enterasys.com]
Sent: 02 May 2013 04:05 PM
To: Enterasys Customer Mailing List
Subject: Re: [enterasys] - Enterasys Wireless Controller intergration with Enterasys NAC - SNMP error

Hi Simon,

You should also add an ip helper address pointing to NAC's ip address so that NAC can resolve the IP address of the client.

Thanks,
Emre

On Thu, May 2, 2013 at 1:02 PM, Read, Simon <***@nashua-communications.com<mailto:***@nashua-communications.com>> wrote:
Hi All,

Would very much appreciate any feedback or suggestions on the following. I have a C25 and LPA successfully managed in NetSight via SNMPv3. What I am trying to do is create a single NAC VNS that allows access for Authenticated and Unauthenticated, (Guest) devices.

802.1x authenticated users connect to the VNS and can be remediated, no problem.

Unauthenticated users should connect to the VNS and then find themselves directed to NAC's login page when they open a browser. I am seeing in NAC that the connection attempt is, "Accept", but MAC-to-IP Address resolution fails. There are ip helper-addresses on the relevant Core switches VLAN GW that point to the DHCP server, the Layer-3 interface created for the NAC VNS and even the management IP address of the Controller.

I've set debugging for DHCP, IP resolution and SNMP to Verbose and in the tag.log and I am seeing the following error...

DEBUG [SnmpManager] Unable to get SnmpSwitch for IP: 127.0.0.1 sw: null

Has anybody seen this error before and/ or are there any suggestions on what might be causing it?


Kind regards,

Simon Read
Service Engineer


[Nashua Communications EMAIL Logo2.gif]


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<http://www.nashuacommunications.co.za>

* --To unsubscribe from enterasys, send email to ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@enterasys.com<mailto:***@enterasys.com>



--

Emre Kurtman
Enterasys Networks
Cell: +90533 3302766
Email: ***@enterasys.com<mailto:***@enterasys.com>

There is nothing more important than our customers.
[Loading Image...]

* --To unsubscribe from enterasys, send email to ***@unc.edu<mailto:***@unc.edu> with the body: unsubscribe enterasys ***@nashua-communications.com<mailto:***@nashua-communications.com>

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 ***@unc.edu with the body: unsubscribe enterasys gneu-***@gmane.org
Loading...