« Back to Technical Questions

AXP Syslog

Combination View Flat View Tree View
Threads [ Previous | Next ]
Post New Thread
AXP Syslog
Answer
2/4/10 9:23 PM
What are the options for configuring syslog in an AXP blade? We have configured our AXP as follows:
 
app-service TSDS_idev
 bind interface eth0
 bind interface eth0.100
 bind interface eth0.30
 bind interface eth0.40
 bind interface eth0.50
 bind interface eth0.60
 bind interface eth0.80
 bind interface eth1
 hostname rye-axp1
 log level warning
 log server address 166.40.64.45
 exit
 
I guess the above configuration takes care of the application syslog, What are about the AXP blade syslog such as if a sub-interface eth0.16 goes down or Eth1 goes down? Would the AXP generate syslog in that case?
 
Thanks
 
Ashish
Flag

RE: AXP Syslog
Answer
2/5/10 2:08 AM as a reply to ASHISH BHATTACHARJEE.
We do log CLI changes such as shut/no shut to syslog.  The changes are logged at level ¿info¿ so they will show up in messages.log on an NME and SRE but not in messages.log on the flash-based systems i.e. AIM2 or ISM.

If you are using a flash-based system, you will need to direct syslog messages to a remote server to see these messages.
Flag

RE: New Message from ASHISH BHATTACHARJEE in Application eXtension Platform
Answer
2/6/10 4:00 AM as a reply to ASHISH BHATTACHARJEE.
No it would not. You can track interface changes via EEM which would send the change to your application which would then write a systemlog.



Thanks,



Brett

Custom Application Engineer



From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
Sent: Thursday, February 04, 2010 7:23 AM
To: cdicuser@developer.cisco.com
Subject: New Message from ASHISH BHATTACHARJEE in Application eXtension Platform (AXP) - Technical Questions: AXP Syslog



ASHISH BHATTACHARJEE has created a new message in the forum "Technical Questions":
--------------------------------------------------------------
What are the options for configuring syslog in an AXP blade? We have configured our AXP as follows:

app-service TSDS_idev
bind interface eth0
bind interface eth0.100
bind interface eth0.30
bind interface eth0.40
bind interface eth0.50
bind interface eth0.60
bind interface eth0.80
bind interface eth1
hostname rye-axp1
log level warning
log server address 166.40.64.45
exit

I guess the above configuration takes care of the application syslog, What are about the AXP blade syslog such as if a sub-interface eth0.16 goes down or Eth1 goes down? Would the AXP generate syslog in that case?

Thanks

Ashish
--
To respond to this post, please click the following link:
<http://developer.cisco.com/web/axp/forums/-/message_boards/message/1946965>
or simply reply to this email.
Flag

RE: New Message from ASHISH BHATTACHARJEE in Application eXtension Platform
Answer
2/6/10 5:39 AM as a reply to Brett Tiller.
EEM actually only detects changes on the router not in the AXP environment so this would not be a viable solution.  I've written a defect for our engineers to investigate why a log isn't written when the interface state changes in AXP 1.5.2.
Flag