10-16-2007 04:57 AM
I need to change the hostname on a few switches, so I want to the the Parameterized templates in NetConfig.
I've used the following parameter file:
<DEVICE NAME = mySwitch>
<CMDPARAM NAME = hostName>
<value>mySwitch</value>
</CMDPARAM>
</DEVICE>
My template:
hostname $hostName
But the command that is sent to the switch is:
hostname mySwitch.0
Note the .0 at the end. That's not very pretty. Has anyone seen this before?
Kind regards,
Siebe
10-22-2007 08:39 AM
Try this link for more information
10-23-2007 07:55 AM
I have not. What version of RME are you using?
10-23-2007 11:05 AM
I just ran into the same issue. RME 4.0.5.
CLI Output
interface range f0/21-22.0
interface range f0/21-22.0
^
% Invalid input detected at '^' marker.
TSTS02(config)#
switchport access vlan 27
switchport access vlan 27
^
% Invalid input detected at '^' marker.
TSTS02(config)#
10-23-2007 11:32 AM
Interesting. I noticed in the CLI output above that the .0 was only on the first parameter. So I added a comment line with a dummy parameter before that in my template.
The result is still this:
CLI Output
! X for Netconfig.0 problem
TSTS02(config)#
interface range f0/21-22.0
interface range f0/21-22.0
^
% Invalid input detected at '^' marker.
TSTS02(config)#
switchport access vlan 27
switchport access vlan 27
^
% Invalid input detected at '^' marker.
TSTS02(config)#
10-23-2007 11:37 AM
Please enable ConfigJob debugging under RME > Admin > System Preferences > Loglevel Settings, re-run your job, then post the Netconfig job directory under /var/adm/CSCOpx/files/rme/jobs/NetConfigJob (Solaris) or NMSROOT\files\rme\jobs\NetConfigJob (Windows).
10-23-2007 11:54 AM
10-23-2007 12:06 PM
I think I see the bug. However, I cannot post code on the forum. It will take me some time to test this patch, but if you would like to open a service request with TAC, I can send you the patch to try out. Just tell the engineer who gets your SR to contact me.
10-23-2007 12:21 PM
Case 607136311
10-23-2007 07:01 PM
I sent the patch to the engineer you owns the SR. The problem is the way the values are being parsed. The trick is that the line ends with "-22". The parser treats most characters as ordinary characters. However, the '-' was left as a default character. Because of that, when the '-' precedes a numeric value, the resulting string is parsed as a number (-22 in this case). The parser returns numbers in double precision format, thus -22 becomes -22.0.
I have fixed this problem, and local tests show the solution to be effective.
10-24-2007 04:59 AM
That did the trick Joe.
CLI Output
interface range f0/23-24
TSTS02(config-if-range)#
switchport access vlan 4
TSTS02(config-if-range)#
Thanks for the patch!
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: