A realtor is needed as a mediator who assists in fixing up the deals while conducting transactions on behalf of a buyer. There are pros and cons to both of the arguments about whether to hire a realtor or not. 

new homes for sale calgary

Pros of Working with a Real Estate Agent

  1. Real estate agents have professional expertise in the real estate industry. They have a wealth of knowledge and professional advice that can help in navigating the exchange process. 

  2. Realtors help in time and energy saving as realtors can assist in convenience while making the biggest purchase decision. Real estate agents have a fair knowledge of the markets and they can decide the best home for buyers.

  3. Realtors help in handling all the listing communications and also assist in the paperwork. 

  4. They are middlemen and they can be very advantageous while negotiating. Realtors are neutral parties in the process of real estate exchange. 

Cons of Working with a Real Estate Agent

  1. A full-service agent may be very expensive in the exchange process and he can demand hefty commission in turn. An average of 6% commission is the minimum demanded price on the selling price. 

  2. Some realtors manage multiple clients and they are typical business persons, it is therefore needed to diligently ensure the realtor prior buying the property. 

  3. It is not necessary that all the realtors can work as per the standards and meet the deadlines properly. They have their own restraints while working on a specific property. 

  4. Realtors are not the financial advisors they can only recommend the best property as per the requirements. They are not a legal advisor as they can only assist a buyer in their legal holdings, but an additional lawyer is needed to complete the legal formalities.

Click For More Information:- Calgary Real Estate

You can always trust Bosch Hydraulics for getting the top-quality varieties of hydraulic hose fittings online. With its professional experience, its specialists are always attempting at supplying the most brilliant ranges of the hydraulic hoses. Its every product is specially designed by the contemporary production line that is considered avant-garde machinery. The hydraulic hose works quite well for conveying hydraulic fluids at different industries. The Company always remains trustworthy towards quality matters and the experts believe it is the products’ accurate quality that offers it an amazing market repute.

Also, Bosch Hydraulics is an esteemed one in this sector as it is serving its customers the top-quality variety of industrial hydraulic hose fittings online. The produced fittings are of quite high-quality, as well as have withstood the test of time, with sheer ease. The hydraulic hose fittings are best for any type of pressure along with being reliable as an outcome of the server testing they go through as their manufacturing process’s part. Irrespective of the reason behind your purchase of these industrial hydraulic hose fittings, you can rely upon the fact that you are investing in the top-quality product.

Bosch Hydraulics tests its hydraulic hose beyond required regulations for ensuring that the product to which the experts put their name is the best possible one. The hose fittings’ manufacture and design is always a creative procedure, with various production units consistently thriving for testing the products. 

 Wish to know more about industrial hydraulic hose fittings? Kindly visit the website


The Cigar is often categorised on the basis of their country of origin such as Cuba, Nicaragua and Dominican Republic. In addition to this, Cigar is also classified on the basis of the wrapper leaves such as Maduro and natural. These wrappers are also classified on the basis of the region of seeds. Both types of Cigar are available online, and you can buy it from an e-commerce website.

Maduro is a word of Spanish origin that means ripe or mature, and these wrappers were collected from the top of tobacco plants in order to ensure that they get exposure to sun and become dark. It is commonly referred to as the process of fermentation instead of plants location. Maduro wrappers are created with the help of proper moisture and heat provided to them naturally, and due to this it is a time-consuming process, and high level of patience is needed in order to reap them properly.

The speciality of Maduro Cigars includes their dark colour, and rich taste made them different from other types of Cigar. The darkest shades of brown and its speciality of providing a wide range of taste such as mellow flavour, the sweet and hearty taste made its demand in the Cigar lovers. As per the claim of a Cigar smoker, most of the flavour is provided by the wrapper to the Cigar, and use of high-quality premium Maduro wrapper made it different from other Cigars.

The darkening of the shades makes the wrapper more oiler and thicker and make it more noticeable on the roll. Moreover, the intense, juicy, fatty leaf provides a rich taste that helps in improving the experience of smoking. Maduro Cigars for sale can be seen on the various websites due to their slow-burning in harmony and in a wavy manner to enhance the experience of a smoker.

Chicago Cubs merchandise is available in various physical and online stores that are officially licensed by the MLB, starting from Chicago Cubs sweatshirts, Chicago Cubs hats and caps, Chicago Cubs shirts, and more. Numerous designs of Chicago Cubs merchandise are available in the market that is manufactured by authentic manufacturers. The Chicago Cubs gear officially licensed by the MLB demonstrates the authenticity and quality of the product. So, if you wish to have a Chicago Cubs gear that is officially licensed by MLB, you may prefer purchasing the Chicago Cubs merchandise from

You can also buy the Chicago Cubs gear from other renowned online stores, like Sports World Chicago, etc., where you can find a vast range of Chicago Cubs gear that is officially licensed by MLB. When you buy any Chicago Cubs merchandise from online stores, make sure to check the details of the product. It is mentioned in the product details whether the product is licensed by MLB or not. The Chicago Cubs gear manufactured by renowned brands like '47, Majestic, Fanatics, Nike, etc. are mostly licensed by MLB. This demonstrates the quality and genuineness of the Chicago Cubs gear.

When you purchase any Chicago Cubs gear, make sure to buy the merchandise that is licensed by MLB. Get the licensed products from well-known physical stores or online stores, and show your support for the Chicago Cubs. There is numerous Chicago Cubs merchandise available with distinct design and style licensed by MLB, so you have various choices from where you can choose products as per your desire. Get any Chicago Cubs gear, and wear them anywhere you go, to show your support and affection for the Cubs. Wear the Chicago Cubs gear while watching the Cubs' match in the stadium or at home, and relish the game as one team.

With the flow of time, people have been looking for all the things online. That is why looking for all the things online is the best choice to make. All the ones who are thinking to look for Tactical gear, then making the right and suitable choice online help the person accurately.

People who are thinking to look for Tactical gear for their safety should make a reliable choice online. This is the best and most prompt way in which one can enhance the level of safety in the right manner. 

The Tactical gear is easily available in various designs as well as quality online so that the make the right choice possible. Even taking help from the experts can help in landing the better gear without any hassle. 

Try and go through all the details of the site carefully before coming to any conclusion. Even a comparison of the gear on the basis of cost and quality can help in getting the finest product accordingly.

Such tools are required by the ones who like to offer the right support possible. The Tactical gear is easy to wear so that the complete protection is added to the person without taking much time. So, all you need to do is just look up the right site for the durable products.

To know more about the suitable Tactical gear from the online site, then it is suggested to give a look at this >> Buy Tactical Clothing

Adding the right support by opting for the computer desk for the firm is the best choice. It is because these desks help in managing the space of the organization properly. The adjustable computer desk is designed in the best way possible so that they can help in keeping all the things in the right manner without any hassle.

The adjustable computer desk not only provides comfortability but would also provide relaxation and calm while working for hours in front of the screen. They are available in modern designs that are meant to suit every kind of decor. One should make sure that you look for these desks from the reliable site. It is because this is going to offer a reliable desk at the doorstep without any hassle.

There are many online sites that are offering the opting of customization so that the person can give a personal touch on the adjustable computer desk.  The customization helps in adding a personal touch to the furniture in the right manner. So, look for all the facilities that are offered online so that one can make the best choice in less duration of time. But don’t forget to go through the policy of the site before coming to any conclusion possible.

To know more about the adjustable computer desk from the right site possible, then the person is suggested that they should give a look at this >> computer supply store

In case you are going through the phase of premature hair loss, then Full Cap Human Hair Wigs are the most effective solution that helps in making you stay confident of yourself and bringing the positive change. Gone are those days when wigs were the only choice for those people who do not wish to undergo the surgical hair transplant procedure as now the hair systems prove to be the more evolved solution for women and men facing baldness. 

Know the right size of your chosen Affordable human hair wigs so that you can opt for the most suitable one without having an odd look and getting your scalp properly covered. Next, opt for the type of hair as the most effective hair used is the chemically treated human hair. You should not also forget to check out the durability and stay away from synthetic hair as much as possible. Are you usually in front of a camera? Do you wear the handset or hat frequently? These questions are critical because it will assist determine what kind of base as well as the attachment method will be the best suitable for you. 

You have to be most cautious while selecting texture, style, and color while buying Men's hair systems as any little adventure can turn out to be an issue. Also, every face needs a different hair system, and this is why it is vital to know about the correct one that suits your face. 

If you want to know more about Mens hairpieces, kindly visit here - Hair Pieces for Men

Fault Managment и поддержка GNU/Linux

1. Введение.

Есть очень много способов реализовать журналирование событий в GNU/Linux. Рассмотрим один из лучших, с возможностью предварительной фильтрации журналируемых событий и отправкой их по сети на syslog сервер NOC.

Предварительная фильтрация журналируемых событий необходима для предотвращения перегрузки сетевого канала передаваемыми событиями и DDOS сервера NOC.

Чтобы реализовать аудит будем использовать средства ядра Linux, также дополнительные утилиты: iptables, .... для настройки правил отлова событий в сети.  В качестве сервиса журналирования - syslog-ng.

2. Включение аудита выполняемых на сервере команд (Security | Audit | Command).

2.1 Настройка ядра Linux.

На исходные тексты ядра необходимо предварительно наложить патчи после чего, как минимум, включить следующие опции:

2.2 Настройка системы.

Создаём группу для аудита:

# groupadd -g 65111 audit

И добавляем в неё необходимых пользователей:

# usermod -a -G audit noc
# usermod -a -G audit ...

Теперь ядро будет слать в системный журнал все выполняемые пользователями команды. Будьте осторожны, некоторые пользователи сервисов могут выполнять огромное количество команд. Добавляйте только необходимых пользователей!

3. Настройки защиты ядра Linux (Security | Attack | Crack Attemption Detected).

Включаем следующие опции настройки ядра:


Бинарные файлы должны собираться с PIE/SSP (CFLAGS="-fPIE -fstack-protector-all -D_FORTIFY_SOURCE=2" LDFLAGS="-Wl,-z,now -Wl,-z,relro"). Теперь ядро способно определять некоторые виды популярных атак, предотвращать их распространение и информировать нас о произошедшей попытке взлома. Можно отметить в этом разделе больше опций или меньше... Некоторые опции сильно влияют на производительность, которая в свою очередь зависит от аппаратной платформы и поддерживаемых процессором инструкций.

4. Настройки iptables, ... и прочих средств списков контроля доступа (Security | ACL).

Необходимо создать специальные правила журналирования пакетов в iptables со специальными метками. Например для журналирования отброшенных пакетов необходимо последними в цепочках INPUT, FORWARD, OUTPUT добавить соответственно следующие правила:

# iptables -t filter -A INPUT -p ALL -m limit --limit 5/h --limit-burst 3 -j LOG --log-prefix 'iptables INPUT '
# iptables -t filter -A FORWARD -p ALL -m limit --limit 5/h --limit-burst 3 -j LOG --log-prefix 'iptables FORWARD '
# iptables -t filter -A OUTPUT -p ALL -m limit --limit 5/h --limit-burst 3 -j LOG --log-prefix 'iptables OUTPUT ' --log-uid

Количество сетевых событий также может быть огромным, фильтруйте только необходимые, например атака ssh heartbeat:

# iptables -t filter -A INPUT -p tcp --dport 22 -m u32 --u32 "52=0x18030000:0x1803FFFF" -j LOG --log-prefix 'iptables SSH HEARTBEAT '

5. Настройка lm_sensors (Environment)

Устанавливаем в систему пакет lm_sensors с поддержкой sensord. В опции запуска sensord можно добавить "-i 0", так он будет журналировать только тревожные сообщения. Запускаем sensord и добавляем его в вашу систему инициализации.

6. Настройка syslog-ng

Настройка этого сервиса предельно понятна и удобна. Необходимо указать 4 главных параметра: источник событий (source), место назначения событий (destination), фильтр событий (filter) и дать команду журналировать (log). Фильтр событьй должен выбирать только события классифицируемые в NOC! Приведём рабочий пример файла настройки /etc/syslog-ng/syslog-ng.conf, локальные журналы с него удалены:

@version: 3.7
# $Id$
# Syslog-ng default configuration file for Gentoo Linux

@include "scl.conf"

options {

# The default action of syslog-ng is to log a STATS line
# to the file every 10 minutes. That's pretty ugly after a while.
# Change it to every 12 hours so you get a nice daily update of
# how many messages syslog-ng missed (0).
# The default action of syslog-ng is to log a MARK line
# to the file every 20 minutes. That's seems high for most
# people so turn it down to once an hour. Set it to zero
# if you don't want the functionality at all.

source src {

destination NOC { udp("" port(514)); };

filter Environment { facility(daemon) and program("sensord") and level(alert); };
filter Network_Link { facility(kern) and message("^.*: (link up|link down)$"); };
filter Network_LAG { facility(kern) and message("^.*: (Adding slave|Removing slave)"); };
filter Network_NTP { facility(daemon) and program("^ntpd$") and (
message("(now valid|now invalid)$")
or message("adjusting local clock by")
or message("clock is now synced$")
); };
filter Security_ACL { facility(kern) and (
                message("^iptables .*")
                or message("^ebtables .*")
                ); };
filter Security_Attack_Hardened { facility(kern) and (
                message("^PAX: terminating task: ")
                or message("^grsec: banning user with uid ")
                or message("^grsec: bruteforce prevention initiated ")
                or message("^grsec: denied resource overstep ")
                or message("^grsec: denied RWX mmap ")
               or message("^grsec: denied untrusted exec ")
                or message("^grsec: From ")
                ); };
filter Security_Audit_Command { facility(kern) and (
                message("^grsec: chdir to") and not message("^.*uid/euid:0/0 gid/egid:0/0, parent /usr/sbin/(run-crons|cron)")
                or message("^grsec: exec of") and not message("^.*uid/euid:0/0 gid/egid:0/0, parent /usr/sbin/(run-crons|cron)")
                ); };
filter Security_Audit_Cron { facility(cron) and message("^.* CMD .*$") and not message("^.*/usr/sbin/run-crons.*$"); };
filter Security_Authentication { facility(authpriv) and message("^(.*|)pam_unix.*$"); };
filter System { program("^init$") and message("^(Entering|Switching to) runlevel: "); };
filter NOC { filter(Environment)
                or filter(Network_Link)
                or filter(Network_LAG)
or filter(Network_NTP)
                or filter(Security_ACL)
                or filter(Security_Attack_Hardened)
                or filter(Security_Audit_Command)
                or filter(Security_Audit_Cron)
                or filter(Security_Authentication)
                or filter(System)
                ; };
log { source(src); filter(NOC); destination(NOC); };

7. NOC

Теперь необходимо ваш GNU/Linux сервер добавить в NOC Service Activation -> Managed Object, при добавлении выбрать профиль OS.Linux и указать в Trap Source IP адрес сервера.

Если решили добавить новые события с сервера GNU/Linux, то напишите ещё фильтры, у файле настройки /etc/syslog-ng/syslog-ng.conf, выбирающие только необходимые вам события и добавьте их через or в агрегирующий фильтр NOC. Выбранные вами события появятся в Fault Management -> Events как Unknown | Syslog. Далее вам необходимо написать правила классификации событий.


Ишью как модераторы-то джируют!

Или рассказ о модерировании Issues в JIRA.

Назрела потребность добавить порядка в задачах в трекере. 

Собственно трекер:

Пара модераторов: Егор и Сергей.

Права на редактирования задачи и добавляем инфы в поля Component/s & Labels.

Сейчас добавляем в Component/s:

в Labels:

  • профиль, если задача по конкретному профилю, например Cisco.IOS;
  • unknown-event — по необработанным FM-сообщениям;
  • patch — при наличии в задаче патча;
  • security — все про безопасность в ноке;
  • request-sa-script — запрашивается создание скрипта в профиле SA;
  • search — проблемы поиска и одноимённого приложения;
  • new-sa-profile — новый профиль устройств;
  • beefCanned Beef;
  • crash — баг ведет в трейсбэку;
  • get_ — имя скрипта, о котором задача;
  • json — есть json-данные.

Примеры поисковых запросов:

labels = sa AND component IS NULL
component IS NULL AND text ~event_class__name
component IS NULL AND text ~"SNMP Trap" AND status != RESOLVED
labels IS NULL AND text ~dlink AND status NOT IN (RESOLVED, CLOSED)
labels IS NULL AND text ~cisco AND status NOT IN (RESOLVED, CLOSED)
project = NOC AND labels IS NULL AND text ~cisco AND status NOT IN (RESOLVED, CLOSED)
project = NOC AND labels IS NULL AND component IS NULL AND status NOT IN (RESOLVED, CLOSED)
project = NOC AND reporter =  'Ilya Zakharov' AND labels IS NULL AND component IS NULL AND status NOT IN (RESOLVED, CLOSED)


Веллком в комменты с предложениями по Component/s & Labels.


project = NOC AND (labels IS NULL OR component IS NULL) AND status NOT IN (RESOLVED, CLOSED, DONE)

Старые баги:

project = NOC AND status not in (RESOLVED, CLOSED, DONE, FEEDBACK) AND createdDate < 2012-01-01 AND type = Bug

вот еще:

project = NOC AND status not in (RESOLVED, CLOSED, DONE, FEEDBACK) AND type = Bug AND (labels is EMPTY OR component is EMPTY) ORDER BY updatedDate


Записки новичка: перезалить скрипт

Бывает, что нужно поправить файло, а с обновлением потом "непонятки",

или и вовсе я случайно грохнул нужный скрипт sa/profiles/Cisco/IOS/

возвращаем файл к состоянию, зафиксированному в репозитории:

под noc'ом

hg revert sa/profiles/Cisco/IOS/


или точнее:

8[14:38]    zi_rus: TSergey: у тебя неправильное описание, реверт не метит, а вытягирает и репо текущую версию взамен той что лежит на диске. 
            если локальный файл отличается от репозитарного, то hg не может по-нормальному его обновить, вернее она могла бы его зам
8[14:38]    zi_rus: а когда ты ревертишь у тебя файл становится одинаковым
8[14:38]    zi_rus: и апгрейд может нормально дальше пройти
Записки новичка: удаляем конфиг МО

Как-то так:

./noc shell
from noc.lib.gridvcs.gridvcs import *
from noc.lib.gridvcs.manager import *
from import *
CLEAR_CONFIG_MO = {'MO1','MO2',...}
mo = ManagedObject.objects.filter()
for m in mo:
    if in CLEAR_CONFIG_MO:
        print "*************************************"

Понадобилось при работе над get_config, для удаления черновых конфигов.

Записки новичка: консервируем МО

У нас нередко коммутатор получает "вторую жизнь".

По каким-либо причинам мы его демонтируем, помещаем на склад, а спустя некоторое время он возвращается в сеть, как новый объект.

Для NOC`а, однако, это не совсем новый объект, некоторые его свойства он помнит для его предыдущей реинкарнации.

Я правлю это так:

./noc shell
from noc.inv.models.discoveryid import DiscoveryID
from noc.inv.models import *
from import *
MO = {'MO1', 'MO2'}
for m in MO:
    id = ManagedObject.objects.get(name = m).id
        chassis = DiscoveryID.objects.get(object = id)
        print "chassis:", chassis.object, chassis.chassis_mac,         
        # delete chassis 
        print "chassis not found:", m
    for i in Interface.objects.filter(managed_object = id):
                l = Link.objects.get(interfaces = i)
                print "link:",
                # delete link
                print "link not found:", i
        # delete interface

Для добавления железок используются ип адреса из address space managment-assignet addresses. Там же нужно проставить tag. Вот сам скрипт


from import *
from noc.inv.models import *
from noc.ip.models import *
from noc.main.models import SystemNotification
import string
import commands
for i in range(1,10):                          #задаем диапазон сеток
  prf=Prefix.objects.filter(prefix='10.10.'+str(i)+'.0/24',vrf='1') #делим диапазон на сети /24 ( по
  for p in prf:
    if p.tags:
      tags1= ','.join(str(v) for v in p.tags)     #ищем тег сетки 
      adrs=p.nested_address_set                   #поиск найденных адресов
      print tags1
      for a in adrs:
        mo=ManagedObject.objects.filter(address=a.address)  #проверка на наличие mo
        if mo:
           for o in mo:
           print a.address
           ring="ring"+str(int(str(a.address).split('.')[3])//20)                          #доп тег
           cmd="snmpget -v 2c -c public " + str(a.address) + " -O Uvqn"  #вендор
           cmd2="snmpget -v 2c -c public " + str(a.address) + " -O Uvqn" #hostname - будущее имя mo
           name=commands.getoutput(cmd2).replace('"', '')
           if x == ".":               #различные вендоры
           if x == ".":
           if x == ".":            #железку не добавляем
           if x == ".":
            type1="Huawei.VRP" #s2328
           if x.startswith("Timeout"):
           if addpr:
            tags2 = [tags1,ring,type2]
            print tags2
            print addpr
            print name
            m = ManagedObject(name=name.format(a.address),is_managed=True,administrative_domain=AdministrativeDomain.objects.get(name="default"),activator = Activator.objects.get(name='default'),profile_name = type1, tags = tags2, snmp_ro = 'public', object_profile = ManagedObjectProfile.objects.get(name='test1'), scheme = 0, address = a.address, user = 'user', password = 'pass')
                             #запись нового mo
            a.managed_object = m  

Работает через ./noc shell. На выходе куча железок в sa-mo, в которых проставлены вендоры, теги и тд, те сразу начинается сбор статистики.

Код далек от идеала. Например, выдет ошибку, если у мо 2 ип (это поправимо).

  1. Как запихнуть этот код в пируль?
  2. При переносе железки с изменением ип, хотелось бы старый мо удалить и создать новый.
  3. Как применить несколько snmp community?

(Canned BeefNOC-1429)

Есть у меня в использовании несколько коммутаторов DLink DGS-3100-24TG.

Они чуть более исключительные, чем остальные DES-DGS, и для них сделан отдельный профиль DGS3100.

Я допилил для указанного профиля обработку портчэналов, доработка коснулась скриптов get_portchannel и get_interfaces.

Для того, что бы поместить изменения в проект, нужно протестировать скрипты — действительно ли я все учел.

В NOC'е для этого реализован механизм работы с "тушенкой", возможность собрать данные с коммутатора и затем тестировать работу скриптов в отсутствии самого железа.

Обновим "тушенку" из публичного репо:

noc@noc:/opt/noc$ ./noc beef --pull
pulling from
searching for changes
no changes found

Тестируем скрипты:

noc@noc:/opt/noc$ ./noc test --beef-filter=DLink.DGS3100.get_portchannel noc.stop
Ran 0 tests in 0.000s
noc@noc:/opt/noc$ ./noc test --beef-filter=DLink.DGS3100.get_interfaces noc.stop
Ran 0 tests in 0.000s

Ноль тестов? Проверяем, есть ли "тушенка" для наших скриптов.

Данные лежат в /opt/noc/local/

noc@noc:/opt/noc/local/repos/sa/sa_public/DLink/DGS3100$ ls -l
drwxrwxr-x 2 noc noc 4096 Oct 20 14:41 get_chassis_id
drwxrwxr-x 2 noc noc 4096 Oct 20 14:41 get_dom_status
drwxrwxr-x 2 noc noc 4096 Oct 20 14:41 get_interface_status
drwxrwxr-x 2 noc noc 4096 Oct 20 14:41 get_lldp_neighbors
drwxrwxr-x 2 noc noc 4096 Oct 20 14:41 get_mac_address_table
drwxrwxr-x 2 noc noc 4096 Oct 20 14:41 get_version
drwxrwxr-x 2 noc noc 4096 Oct 20 14:41 get_vlans

Видим, что для get_portchannel и get_interfaces нет каталогов.

Значит сделаем локальный репо и протестируем на своих данных.

Пишем где будет наш репо:


enabled = true
type = sa
private = true
repo = /srv/noc/my_repo


noc@noc:/opt/noc$ ./noc beef --list-repo
E P T  Name                 Repo
+ N sa sa_public  
+ N sa my_repo              /srv/noc/my_repo

Готовим "тушенку":

./noc debug-script get_portchannel router1 -o output.json
./noc debug-script get_interfaces  router1 -o output.json
 я делал это так

(DLink DGS-3100 — предварительно сделанный селектор)


./noc shell
from import *
SELECTOR = "DLink DGS-3100"
mos = ManagedObjectSelector.objects.filter(name=SELECTOR)[0]
if mos is not None:
    for m in mos.managed_objects:
        #print, m.platform, m.get_attr("version","")
        txt  = "./noc debug-script get_portchannel " 
        txt += + " -o /home/noc/" 
        txt +=".")[0] + "_get_portchannel_" 
        txt += m.get_attr("version","") + ".json"
        print txt
if mos is not None:
    for m in mos.managed_objects:
        txt  = "./noc debug-script get_interfaces " 
        txt += + " -o /home/noc/" 
        txt +=".")[0] + "_get_interfaces_" 
        txt += m.get_attr("version","") + ".json"
        print txt

получаю строки вида:
./noc debug-script get_portchannel router1 -o /home/noc/s2-5-8_get_portchannel_3.60.44.json
./noc debug-script get_interfaces router1 -o /home/noc/s2-5-8_get_interfaces_3.60.44.json

затем кучей вываливаю их в консоль и через некоторое время получаю "тушенку" в /home/noc/


Делаем каталоги  get_portchannel и get_interfaces в /srv/noc/my_repo, копируем в них полученные файлы json. (json в репо помещается не совсем так, буду корректировать)

Тестируем на наших данных:

noc@noc:/opt/noc$ ./noc test --beef=/srv/noc/my_repo/ noc.stop
Ran 28 tests in 0.014s

Или так:

./noc test --beef=/srv/noc/my_repo/ --beef-filter=DLink.DGS3100.get_portchannel noc.stop
./noc test --beef=/srv/noc/my_repo/ --beef-filter=DLink.DGS3100.get_interfaces noc.stop

Или так, на всей доступной тушенке: и нашей и публичной:

./noc test --beef-filter=DLink.DGS3100.get_portchannel noc.stop
./noc test --beef-filter=DLink.DGS3100.get_interfaces noc.stop


Ура, скрипты корректно работают на всех DGS-3100, которые есть у меня в NOC`е.



Бывает, что "test" ругается на данные, а мы видим, что скрипт корректно отдает данные. В моем случае ругалось на ответ скрипта "[]".

Корректируем данные так:

./noc test --beef=/srv/noc/my_repo/ --fixed-beef-base=/srv/noc/fixed-beef yes

в /srv/noc/fixed-beef будут сформированы файлы, в которых найдена и поправлена ошибка. Копируем эти файлы в репо (нужно угадать какие файлы были ошибочные) и снова тестируемся.

Файлы "тушенки" отправляем на и если все корректно, то их разместят в публичном репо.



Записки новичка: закрытие аварий

Как подсказал zi_rus:


09:36 misak, noc shell в помощь
09:36 from import *
09:36 ac = AlarmClass.objects.get(name='Network | EIGRP | Neighbor Down')
09:36 alarms = ActiveAlarm.objects.filter(alarm_class=ac)
09:36 for a in alarms:
09:36 a.clear_alarm("close")
09:36 from import *
09:36 alarms = ActiveAlarm.objects.filter(vars__peer__in=[''])
09:36 for a in alarms:
09:36 a.clear_alarm("close")
09:36  или так
09:36 from import *
09:36 from import *
09:36 alarms = ActiveAlarm.objects.filter(managed_object=ManagedObject.objects.get(name="bb-zmile").id)
09:36 for a in alarms:
09:36 a.clear_alarm("close")
09:36 5 строк

Закроем такие:

# закрыть 'Network | IMPB | Unauthenticated IP-MAC' с IP = ''
from import *
ac = AlarmClass.objects.get(name='Network | IMPB | Unauthenticated IP-MAC')
alarms = ActiveAlarm.objects.filter(alarm_class=ac)
for a in alarms:
    if a['vars']['ip']=='':