Want PIX to log messages 305001 though 305004, says not found?

Discussion in 'Cisco' started by Scott Townsend, Apr 20, 2005.

  1. I have the following setup:

    logging on
    logging timestamp
    logging trap warnings
    logging host inside <syslog-server>


    I would like to be able to also log messages 305001 though 305004 (see below
    for details of the messages) even though they are at level 6 (informational)

    When I enter
    pix(config)# logging message 305002
    I get:
    syslog 305002 not found

    So how do I get it to log jsut those Messages?


    Scott<-



    %PIX-6-305001: Portmapped translation built for gaddr IP_addr/port laddr
    IP_addr/port

    Explanation This is a connection-related message. This message is logged
    when an xlate is created for outbound traffic using a PAT global address.
    This applies to UDP, TCP, and ICMP packets.

    Action None required.

    %PIX-6-305002: Translation built for gaddr IP_addr to laddr IP_addr

    Explanation This is a connection-related message. This message is logged
    when an xlate is created for outbound traffic using a global address, or for
    either outbound or inbound traffic using a static address.

    Action None required.

    %PIX-6-305003: Teardown translation for global IP_addr local IP_addr

    Explanation This is a connection-related message. This message is logged
    when the PIX Firewall clears a dynamically allocated translation after the
    xlate timeout expires.

    Action None required.

    %PIX-6-305004: Teardown portmap translation for global IP_addr/port local
    IP_addr/port
    Scott Townsend, Apr 20, 2005
    #1
    1. Advertising

  2. In article <1aw9e.3584$>,
    Scott Townsend <scott-i@.-N0-SPAMplease.enm.com> wrote:
    :logging trap warnings

    :I would like to be able to also log messages 305001 though 305004 (see below
    :for details of the messages) even though they are at level 6 (informational)

    :When I enter
    : pix(config)# logging message 305002
    :I get:
    : syslog 305002 not found

    Those messages are obsolete. They were last seen in PIX 6.1.

    Note that using 'logging message' in the form you are using will not
    cause messages to be emitted at a 'logging trap' level lower than is
    usual for the message. 'logging message' in the form you are using
    controls whether messages of that id are -ever- emitted (logging level
    permitting.) In the form you are using, 'logging message' followed
    by an id should be considered as just being there to reset a previous
    'no logging message' command that turned off logging of the message.

    In PIX 6.3, there is a mechanism for allowing a message to be seen
    when the logging level is lower than would normally send out the message.
    You use 'logging message' specifying the id and follow it with
    'level' followed by the new level:

    logging message 306013 level trap

    This artificially moves the given message to the given level, thus
    achieving the result you want.
    --
    Beware of bugs in the above code; I have only proved it correct,
    not tried it. -- Donald Knuth
    Walter Roberson, Apr 20, 2005
    #2
    1. Advertising

  3. Works Great...

    I've altered the level for 305009 through 305012 and they are logging great.
    Just had my web developer add a page to allow me to enter in a date time
    range and just return those events...

    Thank you again!

    Scott<-
    "Walter Roberson" <-cnrc.gc.ca> wrote in message
    news:d463rk$2as$...
    > In article <1aw9e.3584$>,
    > Scott Townsend <scott-i@.-N0-SPAMplease.enm.com> wrote:
    > :logging trap warnings
    >
    > :I would like to be able to also log messages 305001 though 305004 (see
    > below
    > :for details of the messages) even though they are at level 6
    > (informational)
    >
    > :When I enter
    > : pix(config)# logging message 305002
    > :I get:
    > : syslog 305002 not found
    >
    > Those messages are obsolete. They were last seen in PIX 6.1.
    >
    > Note that using 'logging message' in the form you are using will not
    > cause messages to be emitted at a 'logging trap' level lower than is
    > usual for the message. 'logging message' in the form you are using
    > controls whether messages of that id are -ever- emitted (logging level
    > permitting.) In the form you are using, 'logging message' followed
    > by an id should be considered as just being there to reset a previous
    > 'no logging message' command that turned off logging of the message.
    >
    > In PIX 6.3, there is a mechanism for allowing a message to be seen
    > when the logging level is lower than would normally send out the message.
    > You use 'logging message' specifying the id and follow it with
    > 'level' followed by the new level:
    >
    > logging message 306013 level trap
    >
    > This artificially moves the given message to the given level, thus
    > achieving the result you want.
    > --
    > Beware of bugs in the above code; I have only proved it correct,
    > not tried it. -- Donald Knuth
    Scott Townsend, Apr 20, 2005
    #3
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Scott Townsend
    Replies:
    3
    Views:
    436
    Scott Townsend
    Mar 23, 2006
  2. jw 1111111

    Nero not burning on to disc though it says it is.

    jw 1111111, Mar 10, 2005, in forum: Computer Support
    Replies:
    3
    Views:
    484
    I Hate XP
    Mar 11, 2005
  3. Tilman Schmidt

    PIX says "no route" even though there is

    Tilman Schmidt, Jul 4, 2007, in forum: Cisco
    Replies:
    7
    Views:
    1,804
    Tilman Schmidt
    Aug 18, 2007
  4. Tilman Schmidt
    Replies:
    2
    Views:
    542
    Tilman Schmidt
    Sep 17, 2007
  5. Jitin
    Replies:
    0
    Views:
    964
    Jitin
    Nov 26, 2009
Loading...

Share This Page