forum.bitel.ru
http://forum.bitel.ru/

Беда с IP ресурсами
http://forum.bitel.ru/viewtopic.php?f=44&t=7529		 Страница 1 из 1
Автор:  borisk [ 13 дек 2012, 13:16 ]
Заголовок сообщения:  Беда с IP ресурсами
Добрый день!

У меня схема: Switch (opt82) + ME3400 (DHCP relay)
Долгое время у меня работала для клиентов сеть x.x.7.0/24. Клиенты растут, понадобилось расширить. Что сделал:
1) На Cisco изменил маску с x.x.7.254/24 на x.x.7.254/23
2) В IP ресурсах решил сделать грамотно. В существующем ресурсе сеть x.x.7.1-253 закрыл вчерашней датой и добавил новую сеть x.x.6.1 - 7.253.
3) В устройстве добавил описание сети x.x.6.0:255.255.254.0
4) Перезагрузил bgaccess

После этого подключающиеся клиенты не могут получить адреса. В логах bgaccess "No Free IP address found"
Как же мне грамотно расширить маску и мигрировать клиентов на новый ресурс?
Автор:  Amir [ 13 дек 2012, 13:25 ]
Заголовок сообщения:  Re: Беда с IP ресурсами
Адреса выдаются динамически или прописаны на сервисах?
Автор:  borisk [ 13 дек 2012, 13:31 ]
Заголовок сообщения:  Re: Беда с IP ресурсами
Выдаются динамически. Еще я в описании исправил пункт 2, для более точного понимания что я сделал в ресурсах.
Автор:  Amir [ 13 дек 2012, 13:41 ]
Заголовок сообщения:  Re: Беда с IP ресурсами
Ошибка. Но будет работать, если добавить диапазоны дополнительно к существующему.
Автор:  borisk [ 13 дек 2012, 13:53 ]
Заголовок сообщения:  Re: Беда с IP ресурсами
Поправите? Я могу подождать пару дней :)
А если добавлять к существующему... не совсем тогда понимаю как именно соотносится то, что мы прописываем в ip ресурсах и то, что прописывается в релее, особенно в части масок.
Автор:  Amir [ 13 дек 2012, 17:40 ]
Заголовок сообщения:  Re: Беда с IP ресурсами
Выложили обновление. Не забудьте сделать бекап старых библиотек.
Автор:  borisk [ 18 дек 2012, 12:47 ]
Заголовок сообщения:  Re: Беда с IP ресурсами
Наконец-то дошли руки попробовать. Ситуация странная - клиент не может получить адрес и гоняет его по кругу. вот как это выглядит со стороны BGAccess:
Код:
12-18/12:19:06  INFO [dhcpLstnr-p-8-t-23] InetAbstractDhcpProcessor - REQUEST:
Message type: BOOT_REQUEST
Dhcp message type: DHCP Discover{1}
htype: 1, hlen: 6, hops: 1
xid: -413524869, secs: 0, flags: 0
Client IP: 0.0.0.0
Your IP: 0.0.0.0
Server IP: 0.0.0.0
Relay IP: 46.22.7.254
Client MAC: {CC5D4E97F8E1}
  {61}={01CC5D4E97F8E1}
  Parameter request list{55}={1, 3, 6, 12, 15, 28, 33, 42, 121, -7}
  {60}={756468637020312E31392E33}
  Agent information{82}=
    sub{1}={00040FD40000}
    sub{2}={0006B8AF673EE470}

12-18/12:19:06  INFO [dhcpLstnr-p-8-t-23] InetDhcpDevice - Search serv on deviceId: 52 and it's descendants; [I@26473f4c; by mac
12-18/12:19:06  INFO [dhcpLstnr-p-8-t-23] InetDhcpDevice - Search serv on deviceId: 52; [I@f8caa36; interfaceId: 0
12-18/12:19:06  INFO [dhcpLstnr-p-8-t-23] InetDhcpProcessor - InetServ found: ContractId: 149; servId: 96
        B8AF673EE470:0
        Options [] TariffModuleTreeSet [162:23.12.2011-…; ]
        Device state: 1; optionSet:10
12-18/12:19:06  INFO [dhcpLstnr-p-8-t-23] InetApplication - inetServ[id=96] balance ok: 1606.67 [0]
12-18/12:19:06  INFO [dhcpLstnr-p-8-t-23] InetApplication - TariffOptionMap: {}
12-18/12:19:06  INFO [dhcpLstnr-p-8-t-23] InetDhcpProcessor - IP not found in service. Searching in device...
12-18/12:19:06  INFO [dhcpLstnr-p-8-t-23] InetAbstractDhcpProcessor - RESPONSE:
Message type: BOOT_RESPONSE
Dhcp message type: DHCP Offer{2}
htype: 1, hlen: 6, hops: 1
xid: -413524869, secs: 0, flags: 0
Client IP: 0.0.0.0
Your IP: 46.22.6.1
Server IP: 0.0.0.0
Relay IP: 46.22.7.254
Client MAC: {CC5D4E97F8E1}
  Agent information{82}=
    sub{1}={00040FD40000}
    sub{2}={0006B8AF673EE470}
  Router{3}=46.22.7.254
  Subnet mask{1}=255.255.254.0
  DNS{6}={5040150150401001}
  IP Address Lease Time{51}=900
  Server Identifier{54}={50401004}
  {2}={00005460}
  Domain{15}=tagnet.hn

12-18/12:19:06  INFO [dhcpLstnr-p-8-t-24] InetAbstractDhcpProcessor - REQUEST:
Message type: BOOT_REQUEST
Dhcp message type: DHCP Request{3}
htype: 1, hlen: 6, hops: 1
xid: -413524869, secs: 0, flags: 0
Client IP: 0.0.0.0
Your IP: 0.0.0.0
Server IP: 0.0.0.0
Relay IP: 46.22.7.254
Client MAC: {CC5D4E97F8E1}
  {61}={01CC5D4E97F8E1}
  Requested IP Address{50}=46.22.6.1
  Server Identifier{54}={50401004}
  Parameter request list{55}={1, 3, 6, 12, 15, 28, 33, 42, 121, -7}
  {60}={756468637020312E31392E33}
  Agent information{82}=
    sub{1}={00040FD40000}
    sub{2}={0006B8AF673EE470}

12-18/12:19:06  INFO [dhcpLstnr-p-8-t-24] InetDhcpDevice - Search serv on deviceId: 52 and it's descendants; [I@26473f4c; by mac
12-18/12:19:06  INFO [dhcpLstnr-p-8-t-24] InetDhcpDevice - Search serv on deviceId: 52; [I@f8caa36; interfaceId: 0
12-18/12:19:06  INFO [dhcpLstnr-p-8-t-24] InetDhcpProcessor - InetServ found: ContractId: 149; servId: 96
        B8AF673EE470:0
        Options [] TariffModuleTreeSet [162:23.12.2011-…; ]
        Device state: 1; optionSet:10
12-18/12:19:06  INFO [dhcpLstnr-p-8-t-24] InetDhcpProcessor - Starting connection: InetConnection [id=0-0, iface=52:0, sessId=e75a1c7b, start=18.12.2012 12:19:06, uname=null, addr=46.22.6.1]
12-18/12:19:07  INFO [dhcpLstnr-p-8-t-24] InetConnectionManager - Already added: InetConnection [id=52494-0, iface=52:0, sessId=e75a1c7b, start=18.12.2012 12:19:06, uname=null, addr=46.22.6.1]
12-18/12:19:07  INFO [dhcpLstnr-p-8-t-24] InetAbstractDhcpProcessor - RESPONSE:
Message type: BOOT_RESPONSE
Dhcp message type: DHCP ACK{5}
htype: 1, hlen: 6, hops: 1
xid: -413524869, secs: 0, flags: 0
Client IP: 0.0.0.0
Your IP: 46.22.6.1
Server IP: 0.0.0.0
Relay IP: 46.22.7.254
Client MAC: {CC5D4E97F8E1}
  Agent information{82}=
    sub{1}={00040FD40000}
    sub{2}={0006B8AF673EE470}
  Router{3}=46.22.7.254
  Subnet mask{1}=255.255.254.0
  DNS{6}={5040150150401001}
  IP Address Lease Time{51}=900
  Server Identifier{54}={50401004}
  {2}={00005460}
  Domain{15}=tagnet.hn


и так до бесконечности

А вот как это выглядит со стороны ME3400:
Код:
Dec 18 12:27:49 YEKT: DHCP_SNOOPING: process new DHCP packet, message type: DHCPDISCOVER, input interface: Gi0/2, MAC da: ffff.ffff.ffff, MAC sa: cc5d.4e97.f8e1, IP da: 255.255.255.255, IP sa: 0.0.0.0, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: cc5d.4e97.f8e1
Dec 18 12:27:49 YEKT: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (4052)
Dec 18 12:27:49 YEKT: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan4052.
Dec 18 12:27:49 YEKT: DHCP_SNOOPING: binary dump of option 82, length: 20 data:
0x52 0x12 0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0 0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:27:49 YEKT: DHCP_SNOOPING: binary dump of extracted circuit id, length: 8 data:
0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0
Dec 18 12:27:49 YEKT: DHCP_SNOOPING: binary dump of extracted remote id, length: 10 data:
0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:27:49 YEKT: DHCP_SNOOPING: can't parse option 82 data of the message, it is either in wrong format or not inserted by local switch
Dec 18 12:27:49 YEKT: DHCP_SNOOPING: process new DHCP packet, message type: DHCPOFFER, input interface: Vl4052, MAC da: cc5d.4e97.f8e1, MAC sa: 0024.50e1.5262, IP da: 46.22.6.1, IP sa: 46.22.7.254, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 46.22.6.1, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: cc5d.4e97.f8e1
Dec 18 12:27:49 YEKT: DHCP_SNOOPING: direct forward dhcp replyto output port: GigabitEthernet0/2.
Dec 18 12:27:50 YEKT: DHCP_SNOOPING: process new DHCP packet, message type: DHCPREQUEST, input interface: Gi0/2, MAC da: ffff.ffff.ffff, MAC sa: cc5d.4e97.f8e1, IP da: 255.255.255.255, IP sa: 0.0.0.0, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: cc5d.4e97.f8e1
Dec 18 12:27:50 YEKT: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (4052)
Dec 18 12:27:50 YEKT: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan4052.
Dec 18 12:27:50 YEKT: DHCP_SNOOPING: binary dump of option 82, length: 20 data:
0x52 0x12 0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0 0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:27:50 YEKT: DHCP_SNOOPING: binary dump of extracted circuit id, length: 8 data:
0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0
Dec 18 12:27:50 YEKT: DHCP_SNOOPING: binary dump of extracted remote id, length: 10 data:
0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:27:50 YEKT: DHCP_SNOOPING: can't parse option 82 data of the message, it is either in wrong format or not inserted by local switch
Dec 18 12:27:50 YEKT: DHCP_SNOOPING: process new DHCP packet, message type: DHCPNAK, input interface: Vl4052, MAC da: ffff.ffff.ffff, MAC sa: 0024.50e1.5262, IP da: 255.255.255.255, IP sa: 46.22.7.254, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 10.128.0.2, DHCP giaddr: 46.22.7.254, DHCP chaddr: cc5d.4e97.f8e1
Dec 18 12:27:50 YEKT: DHCP_SNOOPING: can't delete binding because ip address mismatchs, the server dhcp message DHCPNAK will be forwarded but no binding update is performed.
Dec 18 12:27:50 YEKT: DHCP_SNOOPING: direct forward dhcp replyto output port: GigabitEthernet0/2.
Dec 18 12:27:50 YEKT: DHCP_SNOOPING: binary dump of option 82, length: 20 data:
0x52 0x12 0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0 0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:27:50 YEKT: DHCP_SNOOPING: binary dump of extracted circuit id, length: 8 data:
0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0
Dec 18 12:27:50 YEKT: DHCP_SNOOPING: binary dump of extracted remote id, length: 10 data:
0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:27:50 YEKT: DHCP_SNOOPING: can't parse option 82 data of the message, it is either in wrong format or not inserted by local switch
Dec 18 12:27:50 YEKT: DHCP_SNOOPING: process new DHCP packet, message type: DHCPACK, input interface: Vl4052, MAC da: cc5d.4e97.f8e1, MAC sa: 0024.50e1.5262, IP da: 46.22.6.1, IP sa: 46.22.7.254, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 46.22.6.1, DHCP siaddr: 0.0.0.0, DHCP giaddr: 46.22.7.254, DHCP chaddr: cc5d.4e97.f8e1
Dec 18 12:27:50 YEKT: DHCP_SNOOPING: direct forward dhcp replyto output port: GigabitEthernet0/2.
Dec 18 12:27:53 YEKT: DHCP_SNOOPING: process new DHCP packet, message type: DHCPDISCOVER, input interface: Gi0/2, MAC da: ffff.ffff.ffff, MAC sa: cc5d.4e97.f8e1, IP da: 255.255.255.255, IP sa: 0.0.0.0, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: cc5d.4e97.f8e1
Dec 18 12:27:53 YEKT: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (4052)
Dec 18 12:27:53 YEKT: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan4052.
Dec 18 12:27:53 YEKT: DHCP_SNOOPING: binary dump of option 82, length: 20 data:
0x52 0x12 0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0 0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:27:53 YEKT: DHCP_SNOOPING: binary dump of extracted circuit id, length: 8 data:
0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0
Dec 18 12:27:53 YEKT: DHCP_SNOOPING: binary dump of extracted remote id, length: 10 data:
0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:27:53 YEKT: DHCP_SNOOPING: can't parse option 82 data of the message, it is either in wrong format or not inserted by local switch
Dec 18 12:27:53 YEKT: DHCP_SNOOPING: process new DHCP packet, message type: DHCPOFFER, input interface: Vl4052, MAC da: cc5d.4e97.f8e1, MAC sa: 0024.50e1.5262, IP da: 46.22.6.1, IP sa: 46.22.7.254, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 46.22.6.1, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: cc5d.4e97.f8e1
Dec 18 12:27:53 YEKT: DHCP_SNOOPING: direct forward dhcp replyto output port: GigabitEthernet0/2.
Dec 18 12:27:53 YEKT: DHCP_SNOOPING: process new DHCP packet, message type: DHCPREQUEST, input interface: Gi0/2, MAC da: ffff.ffff.ffff, MAC sa: cc5d.4e97.f8e1, IP da: 255.255.255.255, IP sa: 0.0.0.0, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: cc5d.4e97.f8e1
Dec 18 12:27:53 YEKT: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (4052)
Dec 18 12:27:53 YEKT: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan4052.
Dec 18 12:27:53 YEKT: DHCP_SNOOPING: binary dump of option 82, length: 20 data:
0x52 0x12 0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0 0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:27:53 YEKT: DHCP_SNOOPING: binary dump of extracted circuit id, length: 8 data:
0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0
Dec 18 12:27:53 YEKT: DHCP_SNOOPING: binary dump of extracted remote id, length: 10 data:
0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:27:53 YEKT: DHCP_SNOOPING: can't parse option 82 data of the message, it is either in wrong format or not inserted by local switch
Dec 18 12:27:53 YEKT: DHCP_SNOOPING: process new DHCP packet, message type: DHCPNAK, input interface: Vl4052, MAC da: ffff.ffff.ffff, MAC sa: 0024.50e1.5262, IP da: 255.255.255.255, IP sa: 46.22.7.254, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 10.128.0.2, DHCP giaddr: 46.22.7.254, DHCP chaddr: cc5d.4e97.f8e1
Dec 18 12:27:53 YEKT: DHCP_SNOOPING: can't delete binding because ip address mismatchs, the server dhcp message DHCPNAK will be forwarded but no binding update is performed.
Dec 18 12:27:53 YEKT: DHCP_SNOOPING: direct forward dhcp replyto output port: GigabitEthernet0/2.
Dec 18 12:27:53 YEKT: DHCP_SNOOPING: binary dump of option 82, length: 20 data:
0x52 0x12 0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0 0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:27:53 YEKT: DHCP_SNOOPING: binary dump of extracted circuit id, length: 8 data:
0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0
Dec 18 12:27:53 YEKT: DHCP_SNOOPING: binary dump of extracted remote id, length: 10 data:
0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:27:53 YEKT: DHCP_SNOOPING: can't parse option 82 data of the message, it is either in wrong format or not inserted by local switch
Dec 18 12:27:53 YEKT: DHCP_SNOOPING: process new DHCP packet, message type: DHCPACK, input interface: Vl4052, MAC da: cc5d.4e97.f8e1, MAC sa: 0024.50e1.5262, IP da: 46.22.6.1, IP sa: 46.22.7.254, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 46.22.6.1, DHCP siaddr: 0.0.0.0, DHCP giaddr: 46.22.7.254, DHCP chaddr: cc5d.4e97.f8e1
Dec 18 12:27:53 YEKT: DHCP_SNOOPING: direct forward dhcp replyto output port: GigabitEthernet0/2.
Dec 18 12:27:56 YEKT: DHCP_SNOOPING: process new DHCP packet, message type: DHCPDISCOVER, input interface: Gi0/2, MAC da: ffff.ffff.ffff, MAC sa: cc5d.4e97.f8e1, IP da: 255.255.255.255, IP sa: 0.0.0.0, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: cc5d.4e97.f8e1
Dec 18 12:27:56 YEKT: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (4052)
Dec 18 12:27:56 YEKT: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan4052.
Dec 18 12:27:56 YEKT: DHCP_SNOOPING: binary dump of option 82, length: 20 data:
0x52 0x12 0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0 0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:27:56 YEKT: DHCP_SNOOPING: binary dump of extracted circuit id, length: 8 data:
0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0
Dec 18 12:27:56 YEKT: DHCP_SNOOPING: binary dump of extracted remote id, length: 10 data:
0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:27:56 YEKT: DHCP_SNOOPING: can't parse option 82 data of the message, it is either in wrong format or not inserted by local switch
Dec 18 12:27:56 YEKT: DHCP_SNOOPING: process new DHCP packet, message type: DHCPOFFER, input interface: Vl4052, MAC da: cc5d.4e97.f8e1, MAC sa: 0024.50e1.5262, IP da: 46.22.6.1, IP sa: 46.22.7.254, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 46.22.6.1, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: cc5d.4e97.f8e1
Dec 18 12:27:56 YEKT: DHCP_SNOOPING: direct forward dhcp replyto output port: GigabitEthernet0/2.
Dec 18 12:27:56 YEKT: DHCP_SNOOPING: process new DHCP packet, message type: DHCPREQUEST, input interface: Gi0/2, MAC da: ffff.ffff.ffff, MAC sa: cc5d.4e97.f8e1, IP da: 255.255.255.255, IP sa: 0.0.0.0, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: cc5d.4e97.f8e1
Dec 18 12:27:56 YEKT: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (4052)
Dec 18 12:27:56 YEKT: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan4052.
Dec 18 12:27:56 YEKT: DHCP_SNOOPING: binary dump of option 82, length: 20 data:
0x52 0x12 0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0 0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:27:56 YEKT: DHCP_SNOOPING: binary dump of extracted circuit id, length: 8 data:
0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0
Dec 18 12:27:56 YEKT: DHCP_SNOOPING: binary dump of extracted remote id, length: 10 data:
0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:27:56 YEKT: DHCP_SNOOPING: can't parse option 82 data of the message, it is either in wrong format or not inserted by local switch
Dec 18 12:27:56 YEKT: DHCP_SNOOPING: process new DHCP packet, message type: DHCPNAK, input interface: Vl4052, MAC da: ffff.ffff.ffff, MAC sa: 0024.50e1.5262, IP da: 255.255.255.255, IP sa: 46.22.7.254, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 10.128.0.2, DHCP giaddr: 46.22.7.254, DHCP chaddr: cc5d.4e97.f8e1
Dec 18 12:27:56 YEKT: DHCP_SNOOPING: can't delete binding because ip address mismatchs, the server dhcp message DHCPNAK will be forwarded but no binding update is performed.
Dec 18 12:27:56 YEKT: DHCP_SNOOPING: direct forward dhcp replyto output port: GigabitEthernet0/2.
Dec 18 12:27:56 YEKT: DHCP_SNOOPING: binary dump of option 82, length: 20 data:
0x52 0x12 0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0 0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:27:56 YEKT: DHCP_SNOOPING: binary dump of extracted circuit id, length: 8 data:
0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0
Dec 18 12:27:56 YEKT: DHCP_SNOOPING: binary dump of extracted remote id, length: 10 data:
0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:27:56 YEKT: DHCP_SNOOPING: can't parse option 82 data of the message, it is either in wrong format or not inserted by local switch
Dec 18 12:27:56 YEKT: DHCP_SNOOPING: process new DHCP packet, message type: DHCPACK, input interface: Vl4052, MAC da: cc5d.4e97.f8e1, MAC sa: 0024.50e1.5262, IP da: 46.22.6.1, IP sa: 46.22.7.254, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 46.22.6.1, DHCP siaddr: 0.0.0.0, DHCP giaddr: 46.22.7.254, DHCP chaddr: cc5d.4e97.f8e1
Dec 18 12:27:56 YEKT: DHCP_SNOOPING: direct forward dhcp replyto output port: GigabitEthernet0/2.
Dec 18 12:27:59 YEKT: DHCP_SNOOPING: process new DHCP packet, message type: DHCPDISCOVER, input interface: Gi0/2, MAC da: ffff.ffff.ffff, MAC sa: cc5d.4e97.f8e1, IP da: 255.255.255.255, IP sa: 0.0.0.0, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: cc5d.4e97.f8e1
Dec 18 12:27:59 YEKT: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (4052)
Dec 18 12:27:59 YEKT: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan4052.
Dec 18 12:27:59 YEKT: DHCP_SNOOPING: binary dump of option 82, length: 20 data:
0x52 0x12 0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0 0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:27:59 YEKT: DHCP_SNOOPING: binary dump of extracted circuit id, length: 8 data:
0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0
Dec 18 12:27:59 YEKT: DHCP_SNOOPING: binary dump of extracted remote id, length: 10 data:
0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:27:59 YEKT: DHCP_SNOOPING: can't parse option 82 data of the message, it is either in wrong format or not inserted by local switch
Dec 18 12:27:59 YEKT: DHCP_SNOOPING: process new DHCP packet, message type: DHCPOFFER, input interface: Vl4052, MAC da: cc5d.4e97.f8e1, MAC sa: 0024.50e1.5262, IP da: 46.22.6.1, IP sa: 46.22.7.254, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 46.22.6.1, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: cc5d.4e97.f8e1
Dec 18 12:27:59 YEKT: DHCP_SNOOPING: direct forward dhcp replyto output port: GigabitEthernet0/2.
Dec 18 12:27:59 YEKT: DHCP_SNOOPING: process new DHCP packet, message type: DHCPREQUEST, input interface: Gi0/2, MAC da: ffff.ffff.ffff, MAC sa: cc5d.4e97.f8e1, IP da: 255.255.255.255, IP sa: 0.0.0.0, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: cc5d.4e97.f8e1
Dec 18 12:27:59 YEKT: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (4052)
Dec 18 12:27:59 YEKT: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan4052.
Dec 18 12:27:59 YEKT: DHCP_SNOOPING: binary dump of option 82, length: 20 data:
0x52 0x12 0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0 0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:27:59 YEKT: DHCP_SNOOPING: binary dump of extracted circuit id, length: 8 data:
0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0
Dec 18 12:27:59 YEKT: DHCP_SNOOPING: binary dump of extracted remote id, length: 10 data:
0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:27:59 YEKT: DHCP_SNOOPING: can't parse option 82 data of the message, it is either in wrong format or not inserted by local switch
Dec 18 12:27:59 YEKT: DHCP_SNOOPING: process new DHCP packet, message type: DHCPNAK, input interface: Vl4052, MAC da: ffff.ffff.ffff, MAC sa: 0024.50e1.5262, IP da: 255.255.255.255, IP sa: 46.22.7.254, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 10.128.0.2, DHCP giaddr: 46.22.7.254, DHCP chaddr: cc5d.4e97.f8e1
Dec 18 12:27:59 YEKT: DHCP_SNOOPING: can't delete binding because ip address mismatchs, the server dhcp message DHCPNAK will be forwarded but no binding update is performed.
Dec 18 12:27:59 YEKT: DHCP_SNOOPING: direct forward dhcp replyto output port: GigabitEthernet0/2.
Dec 18 12:28:00 YEKT: DHCP_SNOOPING: binary dump of option 82, length: 20 data:
0x52 0x12 0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0 0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:28:00 YEKT: DHCP_SNOOPING: binary dump of extracted circuit id, length: 8 data:
0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0
Dec 18 12:28:00 YEKT: DHCP_SNOOPING: binary dump of extracted remote id, length: 10 data:
0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:28:00 YEKT: DHCP_SNOOPING: can't parse option 82 data of the message, it is either in wrong format or not inserted by local switch
Dec 18 12:28:00 YEKT: DHCP_SNOOPING: process new DHCP packet, message type: DHCPACK, input interface: Vl4052, MAC da: cc5d.4e97.f8e1, MAC sa: 0024.50e1.5262, IP da: 46.22.6.1, IP sa: 46.22.7.254, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 46.22.6.1, DHCP siaddr: 0.0.0.0, DHCP giaddr: 46.22.7.254, DHCP chaddr: cc5d.4e97.f8e1
Dec 18 12:28:00 YEKT: DHCP_SNOOPING: direct forward dhcp replyto output port: GigabitEthernet0/2.
Dec 18 12:28:02 YEKT: DHCP_SNOOPING: process new DHCP packet, message type: DHCPDISCOVER, input interface: Gi0/2, MAC da: ffff.ffff.ffff, MAC sa: cc5d.4e97.f8e1, IP da: 255.255.255.255, IP sa: 0.0.0.0, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: cc5d.4e97.f8e1
Dec 18 12:28:02 YEKT: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (4052)
Dec 18 12:28:02 YEKT: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan4052.
Dec 18 12:28:02 YEKT: DHCP_SNOOPING: binary dump of option 82, length: 20 data:
0x52 0x12 0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0 0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:28:02 YEKT: DHCP_SNOOPING: binary dump of extracted circuit id, length: 8 data:
0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0
Dec 18 12:28:02 YEKT: DHCP_SNOOPING: binary dump of extracted remote id, length: 10 data:
0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:28:02 YEKT: DHCP_SNOOPING: can't parse option 82 data of the message, it is either in wrong format or not inserted by local switch
Dec 18 12:28:02 YEKT: DHCP_SNOOPING: process new DHCP packet, message type: DHCPOFFER, input interface: Vl4052, MAC da: cc5d.4e97.f8e1, MAC sa: 0024.50e1.5262, IP da: 46.22.6.1, IP sa: 46.22.7.254, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 46.22.6.1, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: cc5d.4e97.f8e1
Dec 18 12:28:02 YEKT: DHCP_SNOOPING: direct forward dhcp replyto output port: GigabitEthernet0/2.
Dec 18 12:28:02 YEKT: DHCP_SNOOPING: process new DHCP packet, message type: DHCPREQUEST, input interface: Gi0/2, MAC da: ffff.ffff.ffff, MAC sa: cc5d.4e97.f8e1, IP da: 255.255.255.255, IP sa: 0.0.0.0, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: cc5d.4e97.f8e1
Dec 18 12:28:02 YEKT: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (4052)
Dec 18 12:28:02 YEKT: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan4052.
Dec 18 12:28:02 YEKT: DHCP_SNOOPING: binary dump of option 82, length: 20 data:
0x52 0x12 0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0 0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:28:02 YEKT: DHCP_SNOOPING: binary dump of extracted circuit id, length: 8 data:
0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0
Dec 18 12:28:02 YEKT: DHCP_SNOOPING: binary dump of extracted remote id, length: 10 data:
0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:28:02 YEKT: DHCP_SNOOPING: can't parse option 82 data of the message, it is either in wrong format or not inserted by local switch
Dec 18 12:28:02 YEKT: DHCP_SNOOPING: process new DHCP packet, message type: DHCPNAK, input interface: Vl4052, MAC da: ffff.ffff.ffff, MAC sa: 0024.50e1.5262, IP da: 255.255.255.255, IP sa: 46.22.7.254, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 10.128.0.2, DHCP giaddr: 46.22.7.254, DHCP chaddr: cc5d.4e97.f8e1
Dec 18 12:28:02 YEKT: DHCP_SNOOPING: can't delete binding because ip address mismatchs, the server dhcp message DHCPNAK will be forwarded but no binding update is performed.
Dec 18 12:28:02 YEKT: DHCP_SNOOPING: direct forward dhcp replyto output port: GigabitEthernet0/2.
Dec 18 12:28:02 YEKT: DHCP_SNOOPING: binary dump of option 82, length: 20 data:
0x52 0x12 0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0 0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:28:02 YEKT: DHCP_SNOOPING: binary dump of extracted circuit id, length: 8 data:
0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0
Dec 18 12:28:02 YEKT: DHCP_SNOOPING: binary dump of extracted remote id, length: 10 data:
0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:28:02 YEKT: DHCP_SNOOPING: can't parse option 82 data of the message, it is either in wrong format or not inserted by local switch
Dec 18 12:28:02 YEKT: DHCP_SNOOPING: process new DHCP packet, message type: DHCPACK, input interface: Vl4052, MAC da: cc5d.4e97.f8e1, MAC sa: 0024.50e1.5262, IP da: 46.22.6.1, IP sa: 46.22.7.254, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 46.22.6.1, DHCP siaddr: 0.0.0.0, DHCP giaddr: 46.22.7.254, DHCP chaddr: cc5d.4e97.f8e1
Dec 18 12:28:02 YEKT: DHCP_SNOOPING: direct forward dhcp replyto output port: GigabitEthernet0/2.
sw-distr-vagonka#no debu
Dec 18 12:28:05 YEKT: DHCP_SNOOPING: process new DHCP packet, message type: DHCPDISCOVER, input interface: Gi0/2, MAC da: ffff.ffff.ffff, MAC sa: cc5d.4e97.f8e1, IP da: 255.255.255.255, IP sa: 0.0.0.0, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: cc5d.4e97.f8e1
Dec 18 12:28:05 YEKT: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (4052)
Dec 18 12:28:05 YEKT: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan4052.
Dec 18 12:28:05 YEKT: DHCP_SNOOPING: binary dump of option 82, length: 20 data:
0x52 0x12 0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0 0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:28:05 YEKT: DHCP_SNOOPING: binary dump of extracted circuit id, length: 8 data:
0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0
Dec 18 12:28:05 YEKT: DHCP_SNOOPING: binary dump of extracted remote id, length: 10 data:
0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:28:05 YEKT: DHCP_SNOOPING: can't parse option 82 data of the message, it is either in wrong format or not inserted by local switch
Dec 18 12:28:05 YEKT: DHCP_SNOOPING: process new DHCP packet, message type: DHCPOFFER, input interface: Vl4052, MAC da: cc5d.4e97.f8e1, MAC sa: 0024.50e1.5262, IP da: 46.22.6.1, IP sa: 46.22.7.254, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 46.22.6.1, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: cc5d.4e97.f8e1
Dec 18 12:28:05 YEKT: DHCP_SNOOPING: direct forward dhcp replyto output port: GigabitEthernet0/2.
Dec 18 12:28:05 YEKT: DHCP_SNOOPING: process new DHCP packet, message type: DHCPREQUEST, input interface: Gi0/2, MAC da: ffff.ffff.ffff, MAC sa: cc5d.4e97.f8e1, IP da: 255.255.255.255, IP sa: 0.0.0.0, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: cc5d.4e97.f8e1
Dec 18 12:28:05 YEKT: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (4052)
Dec 18 12:28:05 YEKT: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan4052.
Dec 18 12:28:05 YEKT: DHCP_SNOOPING: binary dump of option 82, length: 20 data:
0x52 0x12 0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0 0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:28:05 YEKT: DHCP_SNOOPING: binary dump of extracted circuit id, length: 8 data:
0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0
Dec 18 12:28:05 YEKT: DHCP_SNOOPING: binary dump of extracted remote id, length: 10 data:
0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:28:05 YEKT: DHCP_SNOOPING: can't parse option 82 data of the message, it is either in wrong format or not inserted by local switchg all
All possible debugging has been turned off
sw-distr-vagonka#
Dec 18 12:28:05 YEKT: DHCP_SNOOPING: process new DHCP packet, message type: DHCPNAK, input interface: Vl4052, MAC da: ffff.ffff.ffff, MAC sa: 0024.50e1.5262, IP da: 255.255.255.255, IP sa: 46.22.7.254, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 10.128.0.2, DHCP giaddr: 46.22.7.254, DHCP chaddr: cc5d.4e97.f8e1
Dec 18 12:28:05 YEKT: DHCP_SNOOPING: can't delete binding because ip address mismatchs, the server dhcp message DHCPNAK will be forwarded but no binding update is performed.
Dec 18 12:28:05 YEKT: DHCP_SNOOPING: direct forward dhcp replyto output port: GigabitEthernet0/2.
Dec 18 12:28:06 YEKT: DHCP_SNOOPING: binary dump of option 82, length: 20 data:
0x52 0x12 0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0 0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:28:06 YEKT: DHCP_SNOOPING: binary dump of extracted circuit id, length: 8 data:
0x1 0x6 0x0 0x4 0xF 0xD4 0x0 0x0
Dec 18 12:28:06 YEKT: DHCP_SNOOPING: binary dump of extracted remote id, length: 10 data:
0x2 0x8 0x0 0x6 0xB8 0xAF 0x67 0x3E 0xE4 0x70
Dec 18 12:28:06 YEKT: DHCP_SNOOPING: can't parse option 82 data of the message, it is either in wrong format or not inserted by local switch
Dec 18 12:28:06 YEKT: DHCP_SNOOPING: process new DHCP packet, message type: DHCPACK, input interface: Vl4052, MAC da: cc5d.4e97.f8e1, MAC sa: 0024.50e1.5262, IP da: 46.22.6.1, IP sa: 46.22.7.254, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 46.22.6.1, DHCP siaddr: 0.0.0.0, DHCP giaddr: 46.22.7.254, DHCP chaddr: cc5d.4e97.f8e1
Dec 18 12:28:06 YEKT: DHCP_SNOOPING: direct forward dhcp replyto output port: GigabitEthernet0/2.


где-то я туплю, но где?
Автор:  borisk [ 18 дек 2012, 12:59 ]
Заголовок сообщения:  Re: Беда с IP ресурсами
Может я вообще зря все это мучаю? Расскажите, пожалуйста, как пересекаются определения dhcp.net.option, то, что выставлено на интерфейсе у dhcp relay и, собственно ip ресурсы? Может мне достаточно просто расширить маску на интерфейсе у релей и завести дополнительную сеть в ip ресурс с маской /24, а не /23 как я хочу?
Автор:  Amir [ 18 дек 2012, 16:56 ]
Заголовок сообщения:  Re: Беда с IP ресурсами
Параметры должны работать, т.е. соотносится косвенно, по параметрам dhcp.net.option находится по выданному адресу, диапазон не обязательно должен совпадать с таковым у IP-ресурса.

По текущей проблеме - а ответ выдается правильный (маска/роутер/днс)?
Автор:  borisk [ 18 дек 2012, 22:32 ]
Заголовок сообщения:  Re: Беда с IP ресурсами
Да, это проверил... все правильно

По dhcp.inet.option - а по какому принципу то прописывается суффикс сети? То есть
dhcp.inet.option.46.22.6.0:255.255.254.0 чему-то должно соответствовать?
Автор:  borisk [ 18 дек 2012, 22:39 ]
Заголовок сообщения:  Re: Беда с IP ресурсами
Кстати, с последним обновлением похоже опять что-то произошло. Предыдущий DHCP спокойно работал на уровне 350 тредов. Этот же уже выкушал 660 и ползет дальше.
Автор:  Amir [ 19 дек 2012, 14:20 ]
Заголовок сообщения:  Re: Беда с IP ресурсами
Цитата:
По dhcp.inet.option - а по какому принципу то прописывается суффикс сети? То есть
dhcp.inet.option.46.22.6.0:255.255.254.0 чему-то должно соответствовать?
Этот параметр будет применяться к выданным ip из подсети 46.22.6.0 mask 255.255.254.0 (46.22.6.0/23).

Цитата:
Кстати, с последним обновлением похоже опять что-то произошло. Предыдущий DHCP спокойно работал на уровне 350 тредов. Этот же уже выкушал 660 и ползет дальше.
Можете дать доступ, посмотреть?
Автор:  borisk [ 19 дек 2012, 14:55 ]
Заголовок сообщения:  Re: Беда с IP ресурсами
sshd запустил
учетные данные с последнего раза не менял
Автор:  Amir [ 19 дек 2012, 15:20 ]
Заголовок сообщения:  Re: Беда с IP ресурсами
Проблема только в количестве потоков или начинает слать что не успевает обрабатывать? \
У вас в inet-access.xml стоит
Код:
<!-- Количество потоков-обработчиков -->
<param name="threadCount">1000</param>
Это означает, что с каждым обработанным DHCP пакетом пул потоков будет увеличиваться, пока не достигнет 1000, затем так и будет держать 1000 потоков для обработки, уменьшать его по какому-то таймауту не будет.
Т.е. в данном случае, общее количество потоков должно достигнуть какого-то максимума, который больше 1000 и на нем остановиться (после сильно не изменяться).
Автор:  borisk [ 19 дек 2012, 23:05 ]
Заголовок сообщения:  Re: Беда с IP ресурсами
А, вон оно что... а я испугался и все увеличивал этот параметр
Страница 1 из 1 Часовой пояс: UTC + 5 часов [ Летнее время ]
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/