Меню

настройка hunt group cisco

ИТ База знаний

Полезно

— Узнать IP — адрес компьютера в интернете

— Онлайн генератор устойчивых паролей

— Онлайн калькулятор подсетей

— Калькулятор инсталляции IP — АТС Asterisk

— Руководство администратора FreePBX на русском языке

— Руководство администратора Cisco UCM/CME на русском языке

— Руководство администратора по Linux/Unix

Навигация

Серверные решения

Телефония

Настройка программных телефонов

Корпоративные сети

Популярное и похожее

Настройка Site-To-Site IPSec VPN на Cisco

Настройка GRE туннеля на Cisco

Настройка IPv4 на оборудовании Cisco

Настройка и обзор Cisco FirePower

Настройка EtherChannel на Cisco

В этой статье мы расскажем как настроить LACP (Link Aggregation Control Protocol) И PAgP (Port Aggregation Protocol), которые носят гордое название EtherChannels — агрегирование каналов.

На самом деле EtherChannel это технология агрегации (объединения) каналов. Это означает, что мы можем объединить несколько линков в один логический, что позволит увеличить пропускную способность между коммутаторами.

Пример использования

В рамках данной схемы мы имеем серверную инфраструктуру, которая подключена в коммутатору распределения (distribution switch) через свой коммутатор. За коммутатором распределения сидят коммутаторы доступы, за которым расположились пользовательские рабочие станции:

Если мы подключим два коммутатор линком в 1ГБ/сек, то потенциально, мы можем столкнуться с проблемой «бутылочного горлышка», то есть узкого места. Тогда пользователи испытают проблемы с доступом к серверной ферме.

Используя технологию EtherChannel, мы можем объединить до 8 интерфейсов (физических) в один логический линк (агрегация портов, Port-Channel) и трафик будет распределяться между физическими портами равномерно (балансируя нагрузку).

В нашем примере мы объединили 4 (четыре) гигабитных линка между рабочими станциями и серверами в один, с пропускной способностью 4ГБ/сек. Это увеличило общую пропускную способность и добавило отказоустойчивость линков!

Не забывайте про STP (Spanning-tree protocol). В случае агрегации портов, мы исключаем STP петли.

Режимы EtherChannel

Каждый из протоколов LACP или PAgP имеет по 3 режима работы, которые определяют режим его активности (инициализировать ли построение агрегации со своей стороны, или ждать сигнал с удаленной стороны):

  • LACP Modes: ON, ACTIVE, PASSIVE;
  • PAgP Modes: ON, DESIRABLE, AUTO;

Давайте посмотрим, в каком из случае будет установлено соединение EtherChannel при различных режимах настройки. Для LACP:

Коммутатор №1 Коммутатор №2 Установится ли EtherChannel?
ON ON Да
ACTIVE ACTIVE/PASSIVE Да
ON/ACTIVE/PASSIVE Not configured (off) Нет
ON ACTIVE Нет
PASSIVE/ON PASSIVE Нет
Коммутатор №1 Коммутатор №2 Установится ли EtherChannel?
ON ON Да
DESIRABLE DESIRABLE/AUTO Да
ON/DESIRABLE/AUTO Not configured (off) Нет
ON DESIRABLE Нет
AUTO / ON AUTO Нет
Настройка

Ок, предположим, что порты с Gi0/0 по Gi0/3 буду использованы для агрегации EtherChannel. Лучше всего настроить логический интерфейс (агрегированный) в качестве транка, чтобы пропускать VLAN между коммутаторами.

Поднимаем LACP

В нашем случае switch1 будет активном (Active) режиме, а switch2 будет в пассивном (Passive) режиме.

Поднимаем PAgP

В этом случае switch1 будет Desirable — режиме, а switch2 будет в автоматическом (Auto) режиме.

Полезные команды

Вот некоторые команды, которые могут понадобиться вам в работе с EtherChannel:

Полезна ли Вам эта статья?

Пожалуйста, расскажите почему?

😪 Нам жаль, что статья не была полезна для вас 🙁 Пожалуйста, если не затруднит, укажите по какой причине? Мы будем очень благодарны за подробный ответ. Спасибо, что помогаете нам стать лучше!

😍 Подпишитесь на нашу еженедельную рассылку, и мы будем присылать самые интересные публикации 🙂 Просто оставьте свои данные в форме ниже.

источник

Cisco Unified Communications Manager Administration Guide, Release 9.0(1)

Book Title

Cisco Unified Communications Manager Administration Guide, Release 9.0(1)

Chapter Title

View with Adobe Reader on a variety of devices

Results

Chapter: Line group setup

Line group setup

This chapter provides information to add or delete a line group or to add directory numbers to or to remove directory numbers from a line group.

For additional information, see topics related to understanding route plans in the Cisco Unified Communications Manager System Guide .

About line group setup

In Cisco Unified Communications Manager Administration , use the Call Routing > Route/Hunt > Line Group menu path to configure line groups.

A line group allows you to designate the order in which directory numbers are chosen. Cisco Unified Communications Manager distributes a call to idle or available members of a line group based on a call distribution algorithm and on the Ring No Answer Reversion (RNAR) Timeout setting.


Note

Users cannot pick up calls to a DN that belongs to a line group by using the Directed Call Pickup feature.


Tip

Although you can configure an empty line group with no members (directory numbers), Cisco Unified Communications Manager does not support this configuration for routing calls. If the line group contains no members, the hunt list stops hunting when the call gets routed to the empty line group. To avoid this situation, make sure that you configure at least one member in the line group.

Line group configuration tips

You must define one or more directory numbers before configuring a line group.

After you configure or update a line group, you can add or remove members from that line group.

Line group deletion

You cannot delete a line group that one or more route/hunt lists references. To find out which hunt lists are using the line group, in the Line Group Configuration window, choose Dependency Records from the Related Links drop-down list box and click Go. If the dependency records are not enabled for the system, the Dependency Records Summary window displays a message. If you try to delete a line group that is in use, Cisco Unified Communications Manager displays an error message. Before deleting a line group that is currently in use, you must perform the following task:

  • Remove the line group from all hunt lists to which it belongs before deleting the line group.

Tip

To delete line groups and hunt pilots; first, delete the hunt pilot; second, delete the hunt list; and finally, delete the line group.

Related Tasks
Remove route groups from route list Access dependency records

Line group settings

The following table describes the line group settings.

Table 1 Line group settings

Enter a name for this line group. The name can comprise up to 50 alphanumeric characters and can contain any combination of spaces, periods (.), hyphens (-), and underscore characters (_). Ensure that each line group name is unique to the route plan.

Use concise and descriptive names for your line groups. The CompanynameLocationGroup format usually provides a sufficient level of detail and is short enough to enable you to quickly and easily identify a line group. For example, CiscoDallasAA1 identifies a Cisco Access Analog line group for the Cisco office in Dallas.

Enter a time, in seconds, after which Cisco Unified CM will distribute a call to the next available or idle member of this line group or to the next line group if the call is not answered and if the first hunt option, Try next member; then, try next group in Hunt List, is chosen. The RNA Reversion Timeout applies at the line-group level to all members.

Choose a distribution algorithm, which applies at the line-group level, from the options in the drop-down list box:

  • Top Down—If you choose this distribution algorithm, Cisco Unified CM distributes a call to idle or available members starting from the first idle or available member of a line group to the last idle or available member.
  • Circular—If you choose this distribution algorithm, Cisco Unified CM distributes a call to idle or available members starting from the (n+1)th member of a route group, where the nth member is the next sequential member in the list who is either idle or busy but not «down.» If the nth member is the last member of a route group, Cisco Unified CM distributes a call starting from the top of the route group.
  • Longest Idle Time—If you choose this distribution algorithm, Cisco Unified CM only distributes a call to idle members, starting from the longest idle member to the least idle member of a line group.
  • Broadcast—If you choose this distribution algorithm, Cisco Unified CM distributes a call to all idle or available members of a line group simultaneously. See the Note in the description of the Selected DN/Route Partition field for additional limitations in using the Broadcast distribution algorithm.

The default value specifies Longest Idle Time.

For a given distribution algorithm, choose a hunt option for Cisco Unified CM to use if a call is distributed to a member of a line group that does not answer. This option gets applied at the member level. Choose from the options in the drop-down list box:

  • Try next member; then, try next group in Hunt List—If you choose this hunt option, Cisco Unified CM distributes a call to idle or available members starting from the first idle or available member of a line group to the last idle or available member. If unsuccessful, Cisco Unified CM then tries the next line group in a hunt list.
  • Try next member, but do not go to next group—If you choose this hunt option, Cisco Unified CM distributes a call to idle or available members starting from the first idle or available member of a line group to the last idle or available member. Cisco Unified CM stops trying upon reaching the last member of the current line group.
  • Skip remaining members, and go directly to next group—If you choose this hunt option, Cisco Unified CM skips the remaining members of this line group when the RNA reversion timeout value elapses for the first member. Cisco Unified CM then proceeds directly to the next line group in a hunt list.
  • Stop hunting—If you choose this hunt option, Cisco Unified CM stops hunting after trying to distribute a call to the first member of this line group and the member does not answer the call.

For a given distribution algorithm, choose a hunt option for Cisco Unified CM to use if a call is distributed to a member of a line group that is busy. Choose from the options in the drop-down list box:

  • Try next member; then, try next group in Hunt List—If you choose this hunt option, Cisco Unified CM distributes a call to idle or available members starting from the first idle or available member of a line group to the last idle or available member. If unsuccessful, Cisco Unified CM then tries the next line group in a hunt list.
  • Try next member, but do not go to next group—If you choose this hunt option, Cisco Unified CM distributes a call to idle or available members starting from the first idle or available member of a line group to the last idle or available member. Cisco Unified CM stops trying upon reaching the last member of the current line group.
  • Skip remaining members, and go directly to next group—If you choose this hunt option, Cisco Unified CM skips the remaining members of this line group upon encountering a busy member. Cisco Unified CM proceeds directly to the next line group in a hunt list.
  • Stop hunting—If you choose this hunt option, Cisco Unified CM stops hunting after trying to distribute a call to the first busy member of this line group.

For a given distribution algorithm, choose a hunt option for Cisco Unified CM to use if a call is distributed to a member of a line group that is not available. The Not Available condition occurs when none of the phones that are associated with the DN in question is registered. Not Available also occurs when extension mobility is in use and the DN/user is not logged in. Choose from the options in the drop-down list box:

  • Try next member; then, try next group in Hunt List—If you choose this hunt option, Cisco Unified CM distributes a call to idle or available members starting from the first idle or available member of a line group to the last idle or available member. If unsuccessful, Cisco Unified Communications Manager then tries the next line group in a hunt list.
  • Try next member, but do not go to next group—If you choose this hunt option, Cisco Unified CM distributes a call to idle or available members starting from the first idle or available member of a line group to the last idle or available member. Cisco Unified CM stops trying upon reaching the last member of the current line group.
  • Skip remaining members, and go directly to next group—If you choose this hunt option, Cisco Unified CM skips the remaining members of this line group upon encountering the first unavailable member. Cisco Unified CM proceeds directly to the next line group in a hunt list.
  • Stop hunting—If you choose this hunt option, Cisco Unified CM stops hunting after trying to distribute a call to the first unavailable member of this line group.

Line Group Member Information

Find Directory Numbers to Add to Line Group

Choose a route partition for this line group from the drop-down list box. The default value specifies .

If you click Find, the Available DN/Route Partition list box displays all DNs that belong to the chosen partition.

Directory Number Contains

Enter the character(s) that are found in the directory number that you are seeking and click the Find button. Directory numbers that match the character(s) that you entered display in the Available DN/Route Partition box.

Available DN/Route Partition

Choose a directory number in the Available DN/Route Partition list box and add it to the Selected DN/Route Partition list box by clicking Add to Line Group.

Current Line Group Members

Selected DN/Route Partition

To change the priority of a directory number, choose a directory number in the Selected DN/Route Partition list box. Move the directory number up or down in the list by clicking the arrows on the right side of the list box.

To reverse the priority order of the directory numbers in the Selected DN/Route Partition list box, click Reverse Order of Selected DNs/Route Partitions.

For more information about the order of directory numbers in a line group, see topics related to route plans in the Cisco Unified Communications Manager System Guide .

Do not put DNs that are shared lines in a line group that uses the Broadcast distribution algorithm. Cisco Unified CM cannot display all DNs that are shared lines on devices where the DNs are configured as shared lines if the DNs are members of a line group that uses the Broadcast distribution algorithm.

Removed DN/Route Partition

Choose a directory number in the Selected DN/Route Partition list box and add it to the Removed DN/Route Partition list box by clicking the down arrow between the two list boxes.

(list of DNs that currently belong to this line group)

Click a directory number in this list to go to the Directory Number Configuration window for the specified directory number.

When you are adding a new line group, this list does not display until you save the line group.

Related Information

Add members to line group

You can add members to a new line group or to an existing line group. The following procedure describes adding a member to an existing line group.

You must define one or more directory numbers before performing this procedure.

Procedure

Step 1 Choose Call Routing > Route/Hunt > Line Group .
Step 2 Locate the line group to which you want to add a member.
Step 3 If you need to locate a directory number, choose a route partition from the Partition drop-down list box, enter a search string in the Directory Number Contains field, and click Find. To find all directory numbers that belong to a partition, leave the Directory Number Contains field blank and click Find.

A list of matching directory numbers displays in the Available DN/Route Partition list box.

Step 4 In the Available DN/Route Partition list box, choose a directory number to add and click Add to Line Group to move it to the Selected DN/Route Partition list box. Repeat this step for each member that you want to add to this line group.
Step 5 In the Selected DN/Route Partition list box, choose the order in which the new directory number(s) is to be accessed in this line group. To change the order, click a directory number and use the Up and Down arrows to the right of the list box to change the order of directory numbers.
Step 6 Click Save to add the new directory numbers and to update the directory number order for this line group.

Related Information

Remove members from line group

You can remove members from a new line group or from an existing line group. The following procedure describes removing a directory number from an existing line group.

источник

Читайте также:  настройки cura для anet a6