Is it possible to direct SNMP traffic to a specific physical port on a EWC C5210?

[Christopher_Tay]

I am having trouble getting Extreme Management Center to receive SNMP traffic from my 2 C5210 controllers.
I am currently only using the 2 10 Gig fibre ports. 1 is used for the VNS VLANs. All of them are tagged and the port is not set as phyisical and does not have management traffic allowed. The other is used for APs. The port is untagged and set as physical with allow management traffic.
We use this port and network to access the controller GUIs.
NetSight is on a different subnet than the AP network but it is in the same router and the same router table.
NetSight can not see the SNMP traffic coming from the controller and will not discover the controllers
When I place an X440 switch on the AP subnet NetSight can discover it and display its information.
When I attach the management port to the same subnet as NetSight it is discovered and full information seems to be able to be retrieved in the console but not in OneView which still shows the controllers as down in the Wireless Dashboard
I do not want to use the Management Port as most documentation says not to.
I have the 2 copper ports available. Would it help to configure one of them as a physical port and connect it directly to the subnet that NetSIght is on? Is this advisable?

Thank you for your help.

[Christopher_Tay]

Hello Craig,

The NetSight is not behind the gateway of that default route. That is the subnet we have the APs on. The NetSight is on subnet 172.16.10.0/24
The subnets are on the same router table and share the same default route. Other devices, such as an X440 switch are on the 172.16.16.0 subnet and can contact NetSight but not the controller.

[Craig_Guilmette]

https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-configure-SNMPv3-on-V2110

[Craig_Guilmette]

Hello Chris
If you admin port has an IP in the same subnet as your Netsight server you will need to change that IP back to the default 192.168.10.1 (assuming your Netsight is not in that subnet) and reboot the controller to clear that route up. Assuming the Netsight Server is behind the same default gateway as your default route of 172.16.16.1 the IP connectivity should be fine. Then refer to this: https://gtacknowledge.extremenetworks.com/articles/Solution/No-controllers-are-configured-for-OneVie...

[Christopher_Tay]

Hi Ronald,

Yes I am able to ping the physical port IP on each controller from the CLI of the EMC

In the routing protocols I only have the 1 route to the gateway of the AP subnet

[Ronald_Dvorak]

Hi Chris,

is there a route added in the controller to reach the EMC subnet ?
Could you ping the controller AP interface from EMC ?

You'd add a route in ....
GUI > controller > network > routing protocols

-Ron