NetXMS Support Forum

Tam kak-to hitree parametri bili v kstat, k sozaleniju iz golovi tochno ne pomnju a sun'a pod rukoj net... Poprobuj

kstat bge:0::link_up

ili cherez ndd:

ndd /dev/bge0 link_status

P.S. You can also try to setup ODBC and use odbc.ddr instead of mssql.ddr.

Best regards,
Victor

A cherez kstat mozno li dlja etogo interfeisa poluchit' parametr "link_up"? I esli mozno, to on pravil'nij ili net?

Just check it on my laptop (the only difference is that it's Windows Vista not Windows Server 2003). It's not working out of the box, but start to work when I enable TCP/IP in SQL Server Configuration Manager (see attached screenshot). Do you have the same settings? Also, when installing, did you select "Microsoft SQL DB-library" component?

Best regards,
Victor

Vrode ispravil. Esli zamenit' prilozennij fail v src/server/core i peresobrat', to dolzno rabotat'.

Pohoze na bug v agente. A chto skazet

nxget server_ip Net.Interface.Link(bge0)

?

I chto za operacionka na servere?

Quote from: prx on November 15, 2007, 09:46:29 AM
Было бы здорово добавить функцию изменения статуса всех дочерних объектов на Managed/Unmanaged.

Можно выбрать объект ноды, закладку Subordinates, выделить все нужные объекты и сделать им Manage/Unmanage.

Т.е. статус объекта интерфейса bge0 все время CRITICAL?

Hello!

Sorry for delay with reply, was really busy last weeks... Just download SQL 2005 Express, will check it this weekend.

Best regards,
Victor

Да, это баг. В следующей версии исправим.

4 - это статус CRITICAL, не обязательно это node down. Такой статус будет если есть активный аларм со статусом CRITICAL или один из интерфейсов в down'e.

А что выдает

nxget -l localhost Net.InterfaceList

? Dolzen davat' spisok interfeisov.

Пока нет, всю неделю не до того было... На выходных займусь.

Aga, a mi parsim (v osnovnom dlja togo chtobi svjazat' s ob'ektom node), bol'she intellekta - bol'she problem Zaregistriroval v bugtracker'e kak issue #199, budu ispravljat'.

Citata iz RFC3164 (The BSD syslog Protocol), napisana chelovekom iz Cisco:

Quote
The HEADER contains two fields called the TIMESTAMP and the HOSTNAME.
   The TIMESTAMP will immediately follow the trailing ">" from the PRI
   part and single space characters MUST follow each of the TIMESTAMP
   and HOSTNAME fields.  HOSTNAME will contain the hostname, as it knows
   itself.  If it does not have a hostname, then it will contain its own
   IP address.  If a device has multiple IP addresses, it has usually
   been seen to use the IP address from which the message is
   transmitted.  An alternative to this behavior has also been seen.  In
   that case, a device may be configured to send all messages using a
   single source IP address regardless of the interface from which the
   message is sent.  This will provide a single consistent HOSTNAME for
   all messages sent from a device.

   The TIMESTAMP field is the local time and is in the format of "Mmm dd
   hh:mm:ss" (without the quote marks) where:

         Mmm is the English language abbreviation for the month of the
         year with the first character in uppercase and the other two
         characters in lowercase.  The following are the only acceptable
         values:

         Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec

         dd is the day of the month.  If the day of the month is less
         than 10, then it MUST be represented as a space and then the
         number.  For example, the 7th day of August would be
         represented as "Aug  7", with two spaces between the "g" and
         the "7".

         hh:mm:ss is the local time.  The hour (hh) is represented in a
         24-hour format.  Valid entries are between 00 and 23,
         inclusive.  The minute (mm) and second (ss) entries are between
         00 and 59 inclusive.

   A single space character MUST follow the TIMESTAMP field.

Ni slova pro vozmoznost' takogo formata.