[rancid] XRRANCID with CRS-1 devices
Mack, David A (Dave)
dmack at verizon.com
Tue Aug 23 17:26:48 UTC 2011
All,
As I progress with our new install of Rancid version 2.3.6 I am taking a close look at how the xrrancid script handles CRS-1 routers running IOS-XR. We have single and multi-chassis CSR-1 systems currently running IOS-XR 3.9. What I am seeing is that some of the commands syntax are not supported on the device at all and others are not pulling all the information that they might. In the hopes that it might help improve this script, I have listed my observations below:
1) Show Version
Is not picking up the following:
2 Management Ethernet
192 GigabitEthernet
95 SONET/SDH
95 Packet over SONET/SDH
1019k bytes of non-volatile configuration memory.
76170M bytes of hard disk.
2049888k bytes of disk0: (Sector size 512 bytes).
It is also showing the processor as
!Chassis type: CRS-16/S - a CRS-16/S router
!CPU: 7457
Where the raw output is this:
cisco CRS-16/S (7457) processor with 4194304K bytes of memory.
7457 processor at 1197Mhz, Revision 1.2
So perhaps we could make it more descriptive?
2) show redundancy secondary
That syntax is not supported on the CRS-1:
RP/0/RP0/CPU0:ROUTER#show redundancy secondary
^
% Invalid input detected at '^' marker.
RP/0/RP0/CPU0:ROUTER#show redundancy ?
location Location to display
statistics Redundancy statistics information
summary Show summary of all redundant node pairs
trace Show redundancy trace data
| Output Modifiers
<cr>
3) admin show env all output
None of the output of this command is making into the output from xrrancid
4) show diag chassis-info
This syntax is also not supported on the CRS-1
RP/0/RP0/CPU0:ROUTER#sh diag ?
0/0/CPU0 Fully qualified location specification
0/1/CPU0 Fully qualified location specification
0/11/CPU0 Fully qualified location specification
0/12/CPU0 Fully qualified location specification
0/13/CPU0 Fully qualified location specification
0/14/CPU0 Fully qualified location specification
0/15/CPU0 Fully qualified location specification
0/2/CPU0 Fully qualified location specification
0/3/CPU0 Fully qualified location specification
0/4/CPU0 Fully qualified location specification
0/5/CPU0 Fully qualified location specification
0/6/CPU0 Fully qualified location specification
0/8/CPU0 Fully qualified location specification
0/9/CPU0 Fully qualified location specification
0/RP0/CPU0 Fully qualified location specification
0/RP1/CPU0 Fully qualified location specification
WORD Fully qualified location specification
WORD Partially qualified location specification
details display more details than the normal show diag
summary display a summary (one line per slot) of the chassis
| Output Modifiers
<cr>
5) show controllers
This command requires an argument on the CRS-1:
RP/0/RP0/CPU0:ROUTER#sh controllers
% Incomplete command.
RP/0/RP0/CPU0:ROUTER#sh controllers ?
ATM ATM Network Interface(s)
E1 E1 Port controller(s)
E3 E3 Port controller(s)
GigabitEthernet GigabitEthernet/IEEE 802.3 interface(s)
MgmtEth Ethernet/IEEE 802.3 interface(s)
MgmtMultilink Controller for the management of multilink interfacess
POS Packet over SONET/SDH network interface(s)
SONET SONET/SDH Port controller(s)
T1 T1 Port controller(s)
T3 T3 Port controller(s)
asic Select ASIC to peek & poke.
asic-scan Generic ASIC Scan
cpuctrl Show commands for the cpuctrl ASIC
egressq Egressq show commands
egressq Show Egress Queue Manager information
fabricq Fabric queue ASIC show screens.
fia Display Fabric Interface ASIC (FIA) information
ingressq Show commands for the ingressq queueing ASIC.
karachi Karachi Framer information
null show commands for null interface
plim PLIM Information
plim-oc768 OC768 PLIM information
pm Show commands for Platform-mgr.
pse Packet Switching Engine information
services show PLIM services Information
system System controller information
6) show vlan
This command also requires an argument on the CRS-1:
RP/0/RP0/CPU0:ROUTER#sh vlan
% Incomplete command.
RP/0/RP0/CPU0:ROUTER#sh vlan ?
interface VLAN interface status and configuration
tags VLAN tag allocation
trunks VLAN trunks status and configuration
7) We should also have the command "admin show running-config" added. The reason for this is that on multi-chassis systems each chassis has it S/N entered and is assigned a rack number. In addition, fabric chassis information is recorded here.
Single chassis
RP/0/RP0/CPU0:ROUTER#admin show running-config
Building configuration...
!! IOS XR Admin Configuration 3.9.0
username root
group root-system
group cisco-support
secret <removed>
!
aaa authentication login remote local
end
Multi-chassis
RP/0/RP0/CPU0:ROUTER#admin show run
Building configuration...
!! IOS XR Admin Configuration 3.9.0
username root
group root-system
group cisco-support
secret 5 <removed>
!
aaa authentication login remote local
dsc serial TBA12380069 rack 240
dsc serial TBA12380105 rack 0
dsc serial TBM15055938 rack 1
controllers fabric plane 0
oim count 1
oim width 1
oim instance 0 location F0/SM9/FM
!
controllers fabric plane 1
oim count 1
oim width 1
oim instance 0 location F0/SM6/FM
!
controllers fabric plane 2
oim count 1
oim width 1
oim instance 0 location F0/SM3/FM
!
controllers fabric plane 3
oim count 1
oim width 1
oim instance 0 location F0/SM0/FM
!
controllers fabric plane 4
oim count 1
oim width 1
oim instance 0 location F0/SM12/FM
!
controllers fabric plane 5
oim count 1
oim width 1
oim instance 0 location F0/SM15/FM
!
controllers fabric plane 6
oim count 1
oim width 1
oim instance 0 location F0/SM18/FM
!
controllers fabric plane 7
oim count 1
oim width 1
oim instance 0 location F0/SM21/FM
!
end
If anyone wants to look into these issues, I will be more than happy to work with them and provide output/feedback!
Thanks!
Dave
More information about the Rancid-discuss
mailing list