Настройка VLANов- Configuring VLANs

[Endspiel]

Здравствуйте.  Испытываю некоторые проблемы при настройки VLANов на HP Office Connect 1920S, JL381A.

Имеется 1 cisco router, 1 core switch 5406rzl2, 2 mobility controller 7205, 22 штуки 2930F JL259A и около 100 штук этих 1920S.

Суть проблемы заключается в следующем:

Я пробросил вланы на 1920S транком, на самом свитче настроил пару партов транком с натив вланом 101 для AP305 и влан 202 для раздачи сети под wifi, и попытался настроить остальные порты под access vlan 202.

Wi-Fi аппараты получили свои айпи и раздают сеть нормально. Access же не работает, оборудование не получает ip по dhcp (телики, компы, и т.д.). При этом на тестовом свитче у меня все отлично работает. Прилагаю startup-conf:

Google Translated:

Hello. I'm experiencing some problems when setting up VLANs on HP Office Connect 1920S, JL381A.

There is 1 cisco router, 1 core switch 5406rzl2, 2 mobility controller 7205, 22 pieces 2930F JL259A and about 100 pieces of these 1920S.

The problem lies in the following:

I threw the Vlans on a 1920S trunk, at the switch itself I set up a pair of desks with a trunk with a native 101 for the AP305 and 202 for distributing the network under wifi, and tried to configure the remaining ports under access vlan 202.

Wi-Fi devices got Their IP and give out the network normally. Access does not work, the hardware does not receive ip by dhcp (tellys, computers, etc.). At the same time on the test switch, everything works fine for me. Startup-conf:

!Current Configuration:
!
!System Description "HPE OfficeConnect Switch 1920S 24G 2SFP JL381A, PD.01.05, Linux 3.6.5-ac96795c, U-Boot 2012.10-00118-g3773021 (Oct 11 2016 - 15:39:54)"
!System Software Version "PD.01.05"
!System Up Time          "0 days 0 hrs 34 mins 12 secs"
!Additional Packages     HPE QOS,HPE IPv6 Management,HPE Routing
!Current SNTP Synchronized Time: SNTP Client Mode Is Disabled
!
network protocol none
network parms 172.30.0.216 255.255.255.0 172.30.0.1
vlan database
vlan 100-101,202
vlan name 100 "management"
exit
network mgmt_vlan 100
ip telnet server enable
configure
sntp server "46.19.96.19"
!clock timezone 4 minutes 0
clock timezone id 57
time-range Schedule-1
exit
time-range Schedule-2
exit
username "admin" password 888 level 15 encrypted
no username guest
line console
exit
line telnet
exit
line ssh
exit
snmp-server sysname "SW3502"
snmp-server location "28 Floor, apartment 02"
snmp-server contact "Endspiel"
!
interface 1
vlan participation include 100-101,202
vlan tagging 100-101,202
exit
interface 2
vlan pvid 202
vlan participation exclude 1
vlan participation include 202
exit
interface 3
vlan pvid 202
vlan participation exclude 1
vlan participation include 202
exit
interface 4
vlan pvid 202
vlan participation exclude 1
vlan participation include 202
exit
interface 5
vlan pvid 202
vlan participation exclude 1,100
vlan participation include 202
exit
interface 6
vlan pvid 202
vlan participation exclude 1,100
vlan participation include 202
exit
interface 7
vlan pvid 202
vlan participation exclude 1,100
vlan participation include 202
exit
interface 8
vlan pvid 202
vlan participation exclude 1
vlan participation include 202
exit
interface 9
vlan pvid 202
vlan participation exclude 1
vlan participation include 202
exit
interface 10
vlan pvid 202
vlan participation exclude 1
vlan participation include 202
exit
interface 11
vlan pvid 202
vlan participation exclude 1
vlan participation include 202
exit
interface 12
vlan pvid 202
vlan participation exclude 1
vlan participation include 202
exit
interface 13
vlan pvid 202
vlan participation exclude 1
vlan participation include 202
exit
interface 14
vlan pvid 202
vlan participation exclude 1
vlan participation include 202
exit
interface 15
vlan pvid 202
vlan participation exclude 1
vlan participation include 202
exit
interface 16
vlan pvid 202
vlan participation exclude 1
vlan participation include 202
exit
interface 17
vlan pvid 202
vlan participation exclude 1
vlan participation include 202
exit
interface 18
vlan pvid 202
vlan participation exclude 1
vlan participation include 202
exit
interface 19
vlan pvid 202
vlan participation exclude 1
vlan participation include 202
exit
interface 20
vlan pvid 202
vlan participation exclude 1
vlan participation include 202
exit
interface 21
vlan pvid 202
vlan participation exclude 1
vlan participation include 202
exit
interface 22
vlan pvid 202
vlan participation exclude 1
vlan participation include 202
exit
interface 23
vlan pvid 101
vlan participation exclude 1
vlan participation include 101,202
vlan tagging 202
exit
interface 24
vlan pvid 101
vlan participation exclude 1
vlan participation include 101,202
vlan tagging 202
exit
exit

Не понимаю в чем может быть проблема при идентичных настройках на тестовом свитче и на этом.

 I do not understand what the problem may be with the identical settings on the test switch and on it.

[Vince-Whirlwind]

Please clarify whether that config is for the working switch or one of the non-working switches.

I assume interface 1 is the uplink, interfaces 23,24 are the downlinks to APs, and the rest are the Access ports.

Troubleshooting DHCP is step 2.

Step 1: patch a device statically configured with a VLAN202 subnet IP address.
--> can it ping its router address?