06-21-2011 05:41 AM
Hi team,
I found out strange thing when comparing running and startup config files on NME-WAE-502-K9. For example the interface running config looks like the following output:
interface GigabitEthernet 1/0
ip address XXXX YYYY
no autosense
bandwidth 1000
full-duplex
exit
interface GigabitEthernet 2/0
ip address XXXX YYYY
exit
!
But startup config looks like:
interface GigabitEthernet 1/0
exit
interface GigabitEthernet 2/0
exit
!
First I thought that I forgot to write the config, but the same situation occured also after "write" command. I tried to upgrade the IOS from 4.2.1 to 4.3.3, without any luck.
Its not a big deal for my environment but I would like to ask if this is done by design on WAAS network modules (this is not the case for standalone WAAS devices).
Many thanks!
Regards,
Stan
06-21-2011 06:10 AM
Hi Stan,
I believe this is because the IP address of the interfaces of the module are pushed by the router when it boots up (by the "service-module ip address X.X.X.X Y.Y.Y.Y" command).
Since the info is already saved in the router config, I guess we don't save it in the startup config of the module itself to prevent the two values from getting out of sync (and this is why you only see this on modules and not on standalone appliances).
Regards,
Nicolas
06-21-2011 06:15 AM
Hi Nicolas,
thanks for the respond. It sounds logical. But I also found out that I see no configuration under Gigabit interfaces even when I download running config from the waas module to tftp server (copy run tftp). And thats strange . Almost sounds like a bug to me.
Regards,
Stan
06-21-2011 06:25 AM
Hi Stan,
I guess it comes from the fact that if we save the configuration of a device, it is to restore it at a later time.
If we saved the IP address of the interface in the output, it would create problems once you would try to restore it as you can see:
NME-WAE-2(config)#interface GigabitEthernet 1/0
NME-WAE-2(config-if)#ip address 2.2.2.2 255.255.255.0
Specified interface is configured from router.
NME-WAE-2(config)#
I agree it is debatable on whether or not this info should be included in the running config and you can see it as a bug, I see it as an implementation choice
Regards,
Nicolas
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide