Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
Duane_Toler
Advisor

VSX provisioning tool - VS topology defined by routes

Jump to solution

Hey folks,

 

Safe to assume this is a bug?

vsx_provisioning_tool -s 192.168.x.y -u admin -o show vd name VS1

"Internal Error: ShowVsParams: unknown value of interfaceTopologyType -"

That VS has interface topology set to "defined by routes".

VSX gateway: R80.40 JHF 120

MDS: R80.40 JHF 125

 

I didn't see anything immediately obvious in later JHF release notes.  TAC?

 

Thanks!

0 Kudos
1 Solution

Accepted Solutions
Duane_Toler
Advisor

TAC said it was fixed in ongoing take158 for r80.40. Release notes now say the same.  Another TAC call said 158 has been stable from what they have been seeing and they expected it to go GA soon. Not official info, of course. 🙂

View solution in original post

0 Kudos
4 Replies
PhoneBoy
Admin
Admin

I’d open a TAC case.

0 Kudos
Martijn
Advisor

Hi,

We had the same on interfaces with topology 'Defined by routes'. To continue our migration, we changed the topology type to 'Defined by network and netmask' and run the vsx_provisioning_tool succesfully.  Then changed the topology to the old setting.

So somehow the tool does not work correctly when the topology is 'Defined by routes'.

Did you call TAC? What was their answer?

Regards,
Martijn

0 Kudos
Duane_Toler
Advisor

TAC said it was fixed in ongoing take158 for r80.40. Release notes now say the same.  Another TAC call said 158 has been stable from what they have been seeing and they expected it to go GA soon. Not official info, of course. 🙂

0 Kudos
Martijn
Advisor

Hi,

We are on R81.10 take 30 on the management and had this issue was indeed solved in take 38.

Thanks,
Martijn

 

0 Kudos