I’m trying to configured AP and SM 5.2 used VLAN but still success, when I trained at motorola Indonesia making VLAN so easy but when doing it at office still not success.
AP configuration : - Configuration Source = SM
- VLAN enable
- Dynamic Learning enable
- Allow only tag frame disable
- VLAN ageing timeout 25
- Management VID 1
- Vlan membership 20 static
SM Configuration : - Dynamic Learning enable
- Allow Frame Types : all frame
- Vlan ageing timeout 25
- Untagged ingress VID 20
- Management VID 1
When SM registred to AP, I can’t remote SM from NIC at my notebook. But when not registred, I can remote the SM. When trained I can remote SM although SM registred to AP.
Please advice
hajid wrote: I’m trying to configured AP and SM 5.2 used VLAN but still success, when I trained at motorola Indonesia making VLAN so easy but when doing it at office still not success.
AP configuration : - Configuration Source = SM
- VLAN enable
- Dynamic Learning enable
- Allow only tag frame disable
- VLAN ageing timeout 25
- Management VID 1
- Vlan membership 20 static
SM Configuration : - Dynamic Learning enable
- Allow Frame Types : all frame
- Vlan ageing timeout 25
- Untagged ingress VID 20
- Management VID 1
When SM registred to AP, I can’t remote SM from NIC at my notebook. But when not registred, I can remote the SM. When trained I can remote SM although SM registred to AP.
Please advice
Where you got 5.2 GHz AP-SM ? in Indonesia, that stuff is illegal :-)
If SM set untagged VID 20 and VID management is 1, so the way to access SM is only via VID 1. If your laptop is behind SM, that laptop is member of VID 20 but SM Management VID is 1, so if SM can't be accessed, it's normal.
regards,
mrdlnf
mrdlnf wrote: [quote="hajid":2f3wqp5z]I’m trying to configured AP and SM 5.2 used VLAN but still success, when I trained at motorola Indonesia making VLAN so easy but when doing it at office still not success.
AP configuration : - Configuration Source = SM
- VLAN enable
- Dynamic Learning enable
- Allow only tag frame disable
- VLAN ageing timeout 25
- Management VID 1
- Vlan membership 20 static
SM Configuration : - Dynamic Learning enable
- Allow Frame Types : all frame
- Vlan ageing timeout 25
- Untagged ingress VID 20
- Management VID 1
When SM registred to AP, I can’t remote SM from NIC at my notebook. But when not registred, I can remote the SM. When trained I can remote SM although SM registred to AP.
Please advice
Where you got 5.2 GHz AP-SM ? in Indonesia, that stuff is illegal :-)
If SM set untagged VID 20 and VID management is 1, so the way to access SM is only via VID 1. If your laptop is behind SM, that laptop is member of VID 20 but SM Management VID is 1, so if SM can't be accessed, it's normal.
regards,
mrdlnf[/quote:2f3wqp5z]
are you in indonesia?
AP --- wireless --- SM --- laptop
when i got training at motorola indonesia using AP SM 5.4 i can remote SM when used vlan. but when i make lab with 5.2 i can't remote SM when registred to AP but when SM not registred to AP i can remote the SM
Another way to answer this (the same as mrdlnf said - he is correct):
Change the Managment VID to 20
Now “both” the SM and Managment are 20
Now your laptop will be able to reach the SM
When we teach the “Advanced Canopy” class (CPT300) we use this as a demo in our introduction to VLANS.
Where did you learn VLANs from Motorola? In Indonesia? Was it in a class or from a Motorola person training individually? I’m trying to see who we need to share this information with…
Thank you!
Charles
Note that if you switch to this configuration (Management 20, Ingress Untagged 20) you will only be able to access the SM from the ethernet side of the module. If you login to your AP’s and attempt to access the SM via its LUID you will not be able to do this unless the AP’s tag outgoing frames with a VID of 20.
I think the best way to do it is leave your Management ID of all modules at 1, that way the AP’s can access all SM’s via their LUID. Purchase a VLAN capable NIC and install it in a laptop or a PC on the Ethernet side of the SM. Set the NIC to tag packets with the VID of the SM.
Maybe someone with more VLAN experience w/ Canopy can follow up. What I just explained is to the best of my knowledge just from reading about Canopy and VLANs. I have only setup a small office demo using VLANs. I don’t have them deployed on our network as of now.
CTCA-info wrote: Another way to answer this (the same as mrdlnf said - he is correct):
Change the Managment VID to 20
Now "both" the SM and Managment are 20
Now your laptop will be able to reach the SM
When we teach the "Advanced Canopy" class (CPT300) we use this as a demo in our introduction to VLANS.
Where did you learn VLANs from Motorola? In Indonesia? Was it in a class or from a Motorola person training individually? I'm trying to see who we need to share this information with...
Thank you!
Charles
i learn VLAN in motorola indonesia class training. the trainer was rangel from philipine.
msmith wrote: Note that if you switch to this configuration (Management 20, Ingress Untagged 20) you will only be able to access the SM from the ethernet side of the module. If you login to your AP's and attempt to access the SM via its LUID you will not be able to do this unless the AP's tag outgoing frames with a VID of 20.
I think the best way to do it is leave your Management ID of all modules at 1, that way the AP's can access all SM's via their LUID. Purchase a VLAN capable NIC and install it in a laptop or a PC on the Ethernet side of the SM. Set the NIC to tag packets with the VID of the SM.
Maybe someone with more VLAN experience w/ Canopy can follow up. What I just explained is to the best of my knowledge just from reading about Canopy and VLANs. I have only setup a small office demo using VLANs. I don't have them deployed on our network as of now.
yach.. now i'm thinking to make VLAN ID at NIC card of PC, maybe you know how to set VLAN ID at NIC card windows XP. i'm trying google but still not getting best website.
The NIC has to support VLAN tagging. If it a standard integrated NIC, I doubt it has VLAN capability. My guess would be that those cards that support VLAN tagging would have some type of software utlity that you use to indicate what VID to tag packets with.