3 PPPoE сервера

[Ева]

В продолжении истории http://forum.nag.ru/forum/index.php?showto...182&hl=BRAS

Стоят для cisco 7301 для терменирования pppoe ssg, l2tp, шейинг. По маршрутизации имею BGP и OSPF.

С завидной пеиодичностью поднимается у все трех загрузка процессора и какая-нибудь, каждый раз разная вываливается из сети (по консоли захожу, в логах ничего криминального нет, висят юзера типа. Есть ругательства на память)

 

Apr 4 05:05:59.011: %SYS-2-MALLOCFAIL: Memory allocation of 268 bytes failed from 0x602E6E08, alignment 32

Pool: I/O Free: 365376 Cause: Memory fragmentation

Alternate Pool: None Free: 0 Cause: No Alternate pool

 

IOS - c7301-adventerprisek9-mz.124-15.T8.bin

 

На каждой где-то в пике по 1400 юзеров с трафиком в Up/Down 50/50 mbps

 

Я так думаю это уязвимость PPPoE какая-то.

Прошу помощи!

 

 

[aidmax]

Попробуйте на коммутаторе настроить L2 ACL на PPPoE, авось зарежет неправильные пппое пакеты. А по существу - пишите запрос в TAC.

[Ева]

А пример можно?

[Ева]

Больше ни у кого нет идей?

[Telesis]

Memory allocation failure means either:

    *      The router has used all available memory (temporarily or permanently), or
    *      The memory has fragmented into such small pieces that the router cannot find a usable available block. This can happen with the processor memory (used by the Cisco Internet Operating System [IOS]) or with the packet memory (used by incoming and outgoing packets).

 

Memory Fragmentation Problem or Bug

This situation means that a process has consumed a large amount of processor memory and then released most or all of it, leaving fragments of memory still allocated either by this process, or by other processes that allocated memory during the problem. If the same event occurs several times, the memory may fragment into very small blocks, to the point where all processes requiring a larger block of memory cannot get the amount of memory that they need. This may affect router operation to the extent that you cannot connect to the router and get a prompt if the memory is badly fragmented.

This problem is characterized by a low value in the "Largest" column (under 20,000 bytes) of the show memory command, but a sufficient value in the "Freed" column (1MB or more), or some other wide disparity between the two columns. This may happen when the router gets very low on memory, since there is no defragmentation routine in the IOS.

If you suspect memory fragmentation, shut down some interfaces. This may free the fragmented blocks. If this works, the memory is behaving normally, and all you have to do is add more memory. If shutting down interfaces doesn't help, it may be a bug. The best course of action is to contact your Cisco support representative with the information you have collected

[aidmax]

А пример можно?

http://www.cisco.com/en/US/products/hw/swi...080470c39.shtml

 

Это пример L2 ACL под пппое переделать несложно

Edited April 7, 2009 by aidmax

[Ева]

Memory allocation failure means either:

    *      The router has used all available memory (temporarily or permanently), or
    *      The memory has fragmented into such small pieces that the router cannot find a usable available block. This can happen with the processor memory (used by the Cisco Internet Operating System [IOS]) or with the packet memory (used by incoming and outgoing packets).

 

Memory Fragmentation Problem or Bug

This situation means that a process has consumed a large amount of processor memory and then released most or all of it, leaving fragments of memory still allocated either by this process, or by other processes that allocated memory during the problem. If the same event occurs several times, the memory may fragment into very small blocks, to the point where all processes requiring a larger block of memory cannot get the amount of memory that they need. This may affect router operation to the extent that you cannot connect to the router and get a prompt if the memory is badly fragmented.

This problem is characterized by a low value in the "Largest" column (under 20,000 bytes) of the show memory command, but a sufficient value in the "Freed" column (1MB or more), or some other wide disparity between the two columns. This may happen when the router gets very low on memory, since there is no defragmentation routine in the IOS.

If you suspect memory fragmentation, shut down some interfaces. This may free the fragmented blocks. If this works, the memory is behaving normally, and all you have to do is add more memory. If shutting down interfaces doesn't help, it may be a bug. The best course of action is to contact your Cisco support representative with the information you have collected

Ну это я читала до обращения сюда

Просто мне кажется нелогичным что одна 73-я держала и не падала так часто, а три с завидной периодичностью валятся и все с данной ошибкой и у всех перед этим возрастает нагрузка процессора на 20-30 процентов.