FAQ-Is the Command Used to Configure the Static Route Changed After the NE40E Is Upgraded from V300R002 to V300R003

Publication Date:  2012-07-27 Views:  87 Downloads:  0
Issue Description

 Q:
Is the command used to configure the static route changed after the NE40E is upgraded from V300R002 to V300R003? 

 

      
Alarm Information

 Null 

 

Handling Process

 A:
The following is the command in V300R002:
ip route-static X.X.X.X { X.X.X.X | INTEGER<0-32> } { STRING<1-256> | STRING<1-256> STRING<1-256> | X.X.X.X }
[ preference INTEGER<1-255> ] [ track bfd-session STRING<1-15> ] [ description TEXT<1-35> ]
The following is the command in V300R003:
ip route-static X.X.X.X { X.X.X.X | INTEGER<0-32> } { STRING<1-256> | STRING<1-256> STRING<1-256> | X.X.X.X }
[ preference INTEGER<1-255> ] [ tag INTEGER<1-4294967295> ] [ track bfd-session STRING<1-15> ] [ description TEXT<1-19> ]

After the NE40E is upgraded from V300R002 to V300R003, the tag parameter is added to the command used to configure a static route. A command can contain a maximum of 256 characters. Since the added tag parameter can contain a maximum of 16 characters (including space characters), the length of the description text is reduced from 35 characters to 19 characters. If the length of the description text is not manually changed to 19 characters, after the upgrade, the first 19 characters in the configured description text are output as the final description information. 

 

Root Cause

 Null 

 

      
Suggestions

 Null 

 

END