Snmp-PrizmEms-windows 2003 r2 server

Hi There

I am new to snmp …
But here is my issue hopefully someone out there can help:)
I have PrizmEms addministrator tool running on a windows 2003 r2 server with no real issues
i have PrizmEms running on my laptop again with no problems
i am able to accept and manager my aps ( 4 of them 900ap)
We have 3 vlan running on our system for the motorola equipment
407,406,402.

After several long talks with tech support we are no furhter ahead.
The Porblem

If i set my configuration source on my ap to bam we are not able to communicate with our SM. ( we are not able to ping etc )
But as sson as set the configuration source to sm i have no issues communicating with the sm

while speaking to tech support we have confirmed that all our info is correct on the ap and the sm for our vlan’s

All our vlan’s are tagged coming from the router
I think that my issue is the way snmp is configured. While reading the very long Prizm 2.1 manual there is a comment on page 70 about setting snmp proxy up and enabling port 61002on the ap…not sure where to do that???

Any help would be helpfull

thanks Malachi

The Sm active configuration is only there when Ap configuration source is set to sm other wise i am unable to see current VID Member set.

Sm
Active Configuration
Untagged Ingress VID : 402
Management VID : 407
SM Management VID Passthrough : Enabled
Dynamic Ageing Timeout : 25
Allow Learning : Yes
Allow Frame Type : All Frame Types

Current VID Member Set:
VID Number Type Age
--------------------------
402 Permanent 0
407 Permanent 0

AP
Active Configuration
Untagged Ingress VID : 1
Management VID : 406
SM Management VID Passthrough : Enabled
Dynamic Ageing Timeout : 25
Allow Learning : No
Allow Frame Type : All Frame Types

Current VID Member Set:
VID Number Type Age
--------------------------
1 Permanent 0
402 Static 0
406 Permanent 0
407 Static 0

can you get into the AP and LUID to it…

is the SM nat enabled/disabled ?

ping the ip we are talking about h RF public…

Remeber that the VLAN settings do not become active until the SM is not registered to AP.

cahange the MVID on the SM to 406 and see what happens, it may be a VLAN routing issue…

vj wrote:
can you get into the AP and LUID to it....

is the SM nat enabled/disabled ?

ping the ip we are talking about h RF public...

Remeber that the VLAN settings do not become active until the SM is not registered to AP.

cahange the MVID on the SM to 406 and see what happens, it may be a VLAN routing issue...



I am able to get to sm thru the luid sollect on the ap
nat is disabled on the sm
changed the Mvid to 406 with no change

doesn’t sound like an SNMP issue… sounds more like vlan configuration…


in prizm when you authenticate or get Prizm to manage the SM, it will override the settings on the SM at time of connection. Hence look at the default config you are pushing out to the SM when it authenticates, check to see if it is using the same vlans…

on your router (assuming cisco) do

sh arp | inc <mac address of SM>

it should tell you what vlan it is seeing it on