Managment routes is not working

[gvpelt]

I am working with css11506 and software 7.30.005

New feature is managment routers over the managment port via command :

ip management route 1.1.1.0 255.255.255.0 <next hop>

if I configer logging, sntp or Tacacs on the subnet 1.1.1.0 its not working.

Do I need more config to make this work?

--error--

(config)# logging host 1.1.1.1 facility 0

%% SYSLOGD cannot go to local I/F, VIP, or APP

Kind Regards,

Gerrit Frans van Pelt

[dcayer]

Is your ethernet management port's IP address configured on the same subnet as ?

Maybe the "show ip route" and "show boot" commands can help you figure out why your management routes don't work.

Good luck,

Dan

[gvpelt]

Yes my managment port is in same subnet as the next hop adress and I Can ping the ntp tacacs and logging managment servers on 1.1.1.1.

/GF

[Gilles Dufour]

you get this error message when you point at yourself.

GILLES# sho boot

!************************ BOOT CONFIG ************************

ip address 1.1.1.1

subnet mask 255.255.255.0

GILLES(config)# logging host 1.1.1.1 facility 7 log-level debug-7

%% SYSLOGD cannot go to local I/F, VIP, or APP

GILLES(config)# logging host 1.1.1.2 facility 7 log-level debug-7

GILLES(config)#

So, make sure you are not pointing to the address you have configured on the CSS.

Regards,

Gilles.

[gvpelt]

Iam not pointing to myself

css01(config)# sh boot

!************************ BOOT CONFIG ************************

ip address 10.133.212.34

subnet mask 255.255.255.224

primary boot-file sg0730005

css01(config)# sh run | grep mana

ip management route 10.129.111.0 255.255.255.0 10.133.212.33

css01(config)# logging host 10.129.111.16 facility 0

%% SYSLOGD cannot go to local I/F, VIP, or APP

css01(config)#

[Gilles Dufour]

ok - thanks for the info.

I verified the same problem in the lab.

I have contacted the developpers to verify if this is expected behavior or not.

Gilles.

[Gilles Dufour]

from developpers, DNS, SNTP, TACACS, and sysloging can only be done to a local device when attached to the management port.

Regards,

Gilles.

[gvpelt]

Thanks for this info.

Do you know if there is already an Request for enhancement?

The new Feature "routing via Management port" is not very useful this way.

Regards

Gerrit Frans

[Gilles Dufour · Accepted solution]

there is no new feature request at this point of time.

I have introduced a bug to modify the error message to be more explicit.

Regards,

Gilles.

[andreas.larsen]

I have to agree the managment port does little or nothing in a bigger company's infrastructure. This should be a "feature" that should be implementerd asap im my opinion. We won't be buying any more of these until this is fixed.

[Gilles Dufour]

We found a workaround.

Apparently, if you configure the logging host first and then the management route than it works and you don't get the error message.

This is however not officially supported.

Gilles.