Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: Alcatel SROS show service id index issue #556

Closed
FragmentedPacket opened this issue Dec 10, 2019 · 2 comments
Closed

Bug: Alcatel SROS show service id index issue #556

FragmentedPacket opened this issue Dec 10, 2019 · 2 comments

Comments

@FragmentedPacket
Copy link
Contributor

ISSUE TYPE
  • Bug Report
Command Output
*A:LAB-12e(R4)# show service id  
<service-id>
 "1001"  "4000"  1001    4000
*A:LAB-12e(R4)# show service id base 
                                ^
MINOR: CLI Invalid service "base".
*A:LAB-12e(R4)# show service id  4000 base 
===============================================================================
Service Basic Information
===============================================================================
Service Id        : 4000                Vpn Id            : 0
Service Type      : VPRN                
Name              : 4000
Description       : (Not Specified)
Customer Id       : 1                   Creation Origin   : manual
Last Status Change: 05/12/2001 02:28:30 
Last Mgmt Change  : 05/12/2001 02:28:30 
Admin State       : Up                  Oper State        : Up
Router Oper State : Up                  
Route Dist.       : 65000:4000          VPRN Type         : regular
Oper Route Dist   : 65000:4000
Oper RD Type      : configured          
AS Number         : 65000               Router Id         : 10.0.0.4
ECMP              : Enabled             ECMP Max Routes   : 1
Max IPv4 Routes   : No Limit            
Auto Bind Tunnel
Resolution        : filter              
Filter Protocol   : rsvp
Weighted ECMP     : Disabled            ECMP Max Routes   : 0
Max IPv6 Routes   : No Limit            
Ignore NH Metric  : Disabled            
Hash Label        : Disabled            
Entropy Label     : Disabled            
Vrf Target        : target:65000:4000   
Vrf Import        : None
Vrf Export        : None
MVPN Vrf Target   : None                
MVPN Vrf Import   : None
MVPN Vrf Export   : None
Car. Sup C-VPN    : Disabled            
Label mode        : vrf                 
BGP VPN Backup    : Disabled            
BGP Export Inactv : Disabled            
SAP Count         : 1                   SDP Bind Count    : 0
VSD Domain        : <none>
-------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------
Identifier                               Type         AdmMTU  OprMTU  Adm  Opr
-------------------------------------------------------------------------------
sap:1/1/7                                null         1514    1514    Up   Down
===============================================================================

Index file:
alcatel_sros_show_service_id_base.textfsm, .*, alcatel_sros, sh[[ow]] serv[[ice]] id ba[[se]]

If changed to the following, it parses correctly:
alcatel_sros_show_service_id_base.textfsm, .*, alcatel_sros, sh[[ow]] serv[[ice]] id (\d+) ba[[se]]

SUMMARY

The command on this version appears to require an ID between id and base and does not return structured data due to Clitable not being able to match the command to the index file and the regex inside of the index file. We'll need to come up with a way to account for both with/without the numeric ID being specified to ensure backwards capability.

@h4ndzdatm0ld
Copy link
Contributor

Thanks for the bug submission.
This command will never be used without specifying a service id numeric value.
The command is only used to view specific service ID information, without specifying a service ID, an error will return.

@jmcgill298
Copy link
Contributor

Thanks @h4ndzdatm0ld

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants