Cisco Explorer 1540 Specifications download pdf (Page 200)

100

101

6-8

Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)

OL-20105-01

Chapter 6 Cisco Unified Serviceability Alarms and CiscoLog Messages

Cisco Unified Serviceability Alarms and CiscoLog Messages

• IPv4 Address—IPv4 address should be represented in dot notation “x.x.x.x”, where x is a decimal

value from 0 to 255 encoded as ASCII text. If an IP address is unknown, “0.0.0.0” (without quotes)

must be used as a place holder. Examples of valid IPv4 addresses are 0.0.0.0 and 212.1.122.11.

Below is an example of a message with an IPv4 address in the HOST field:

11: 212.1.122.11: Jun 13 2003 23:11:52.454 UTC: %BACC-3-BAD_REQUEST: Bad request

received from device [1.2.3.4]. Missing header.

Below is an example of a CiscoLog message when FQDN, hostname or IP are all unknown:

11: 0.0.0.0: Jun 13 2003 23:11:52.454 UTC: %BACC-3-BAD_REQUEST: Bad request received

from device [1.2.3.4]. Missing header.

• IPv6 Address—IPv6 address representation must follow conventions outlined in RFC 3513,

sections 2.2.1, 2.2.2 and 2.2.3. Specifically, all three conventions are supported. Both lower-case

and upper-case letters can be used in the IPv6 address, but the lower-case letters are recommended.

If an IP address is unknown, “0.0.0.0” (without quotes) should be used as the IP address. Examples

of valid IPv6 addresses:

–

1080:0:0:800:ba98:3210:11aa:12dd (full notation)

–

1080::800:ba98:3210:11aa:12dd (use of “::” convention)

–

0:0:0:0:0:0:13.1.68.3 (last 4 octets expanded as in IPv4)

–

0.0.0.0 (unknown FQDN, hostname and IP address )

Below is an example of a message with an IPv6 address in the HOST field:

11: 1080:0:0:800:ba98:3210:11aa:12dd: Jun 13 2003 23:11:52.454 UTC:

%BACC-3-BAD_REQUEST: Bad request received from device [1.2.3.4]. Missing header.

TIMESTAMP Field

The TIMESTAMP field provides date with year, time with milliseconds and a time zone identifier in the

following format:

[ACCURACY]<MONTH> <DAY> <YEAR>

Below are several examples of valid time stamps:

Jun 13 2003 23:11:52.454 UTC

Jun 3 2003 23:11:52.454 UTC

Jun 22 2003 05:11:52.525 -0300

*Feb 14 2003 01:02:03.005 EST

In some cases, it is possible that a device may not have the knowledge of the date and/or time due to

hardware or software limitations. In such circumstances, the following string must be produced in the

TIMESTAMP field: “--- 00 0000 00:00:00.000 ---“. Below is an example of a CiscoLog message from

a device which has no knowledge of date and/or time:

11: host.domain.com: --- 00 0000 00:00:00.000 ---: %BACC-3-BAD_REQUEST: Bad request

received from device [1.2.3.4]. Missing header.

Devices which are not aware of their clock, may choose to provide an uptime as a relative measure of

time. If device is capable of providing uptime, it is recommended that does so as a substitute for

unavailable time stamp. If uptime is provided it must be provided with a standard uptime tag as outlined

in the CiscoLog Standard Tags specification.

Table 6-1 details each field specification.

1 ... 199 200 201 ... 924

Comments to this Manuals

No comments

Cisco Explorer 1540 Specifications Page 200

Comments to this Manuals

Related products and manuals for Digital Video Recorders (DVR) Cisco Explorer 1540