Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Syslogging Help Extreme Summit X250

Status
Not open for further replies.

judgestone

IS-IT--Management
Oct 16, 2006
53
US
I am a Cisco guy, and have all my Cisco Routers/Switches syslogs being sent to my linux syslog server with syslog-ng running on it, and those logs piped to MySql to allow me to view the logs web based with PHP-Syslog-ng, and all works fine.

We just got two Extreme Summit X250's in and I have typed everything I know into them but can't get my logs to show up?

For some reason in the Extreme you have to type the same stuff over and over, or be to specific? I just want my logs that would be equal to my Cisco logs to be sent.

Here is my present Extreme Log Setup:

Log Target : syslog; 192.168.11.37:514 (vr VR-Mgmt), local7
Enabled : yes
Filter Name : DefaultFilter
Match regex : Any
Severity : Info (through Critical)
Format : YYYY/MM/DD HH:MM:SS.hh


Am I off on the Local?, or Severity part? I did change the date format to equal what is set in my SQL DB.

Any help will be greatly appreciated.
 
Are you using the out-of-band (OOB) management port on the rear of the switch? Because you selected VR-Mgmt, so the switch thinks you are right now.

Virtual Router VR-Mgmt is the route table dedicated to the OOB port on the rear of the switch.

If you are using the switch data ports on the front of the switch you need to use VR-Default as follows:

configure syslog 192.168.150.254:514 vr vr-default local7 warning
enable syslog

You need to think of the X250 as a box with two routers inside of it. The VR-MGMT is an independent router and table that is dedicated to the OOB management port in the rear of the switch. The VR-Default is another router and table that is dedicated to routing between VLANs assigned to the front data switch ports on the switch.

Your command is telling the switch. Send Syslog to 192.168.11.37 using the Management port route table.

The switch does not allow routing between the OOB port VR-Mgmt and the VLAN router interfaces VR-Defaut. Hence the name Out-of-Band.

Since the switch has two independent route tables, you must select the one to use based on where your traffic is destined. If the command is sending a packet out the Management port route table, select VR-Mgmt. If the command is sending a packet out the Data port route table, select VR-Default.

This is actually a very powerful feature, but if you are coming over from the Cisco world, it takes some getting used to.

By the way, the same goes for telnet. If you want to telnet to a device reachable on a VLAN assigned to one of the front switch ports you must type:

telnet vr vr-default 10.1.1.100

If you just type...

telnet 10.1.1.100 the switch assumes that you are trying to telnet and send the packet out using the OOB interface on the rear of the switch.

Again, two routers, you have to pick the one that you want the command to apply to.

It gets confusing for newbies because the ping command happens to uses vr-default by default, but telnet uses vr-mgmt by default. So newbies always complain that "ping is working, but telnet is not". No, it works, you just have to select the appropriate route table according to what you are doing. Your always best selecting the appropriate virtual-router and table.

This should help you solve your problem. The only other thing it could be is a missing IP route.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top