Bringing up this new Cisco ASR 9010 with RSP440 and 24x10GE Linecards, running in IOS-XR 6.x.x. Ready to go live anytime soon
Tuesday, 28 May 2019
Bringing up this new baby
Bringing up this new Cisco ASR 9010 with RSP440 and 24x10GE Linecards, running in IOS-XR 6.x.x. Ready to go live anytime soon
Wednesday, 15 May 2019
Wipe out running configuration in Cisco IOS-XR
For IOS, the equivalent command of "write erase" to IOS-XR is the command "commit replace"
RP/0/RSP0/CPU0:ASR9K(config)#commit replace ?
best-effort Commit the configuration changes via best-effort operation
comment Assign a comment to this commit
confirmed Rollback this commit unless there is a confirming commit
force Override the memory checks
label Assign a label to this commit
save-running Save running configuration to a file
show-error Displays commit failures immediately
<cr> Commit the configuration changes via pseudo-atomic operation
RP/0/RSP0/CPU0:ASR9K(config)#commit replace
Tue May 14 14:20:33.387 SGP
This commit will replace or remove the entire running configuration. This
operation can be service affecting.
Do you wish to proceed? [no]: yes
RP/0/RSP0/CPU0:ios(config)#
Sunday, 12 May 2019
Best Practice Configuration for IOS-XR (Part 1)
There are sample best practice commands that need to be configured in IOS-XR devices for additional security.
Global config:
nsr process-failures switchover
tcp path-mtu-discovery
tcp selective-ack
logging console disable
snmp-server ifmib stats cache
ssh server logging
no telnet vrf $vrf-name ipv4 server
ssh client source-interface $$loopback0
logging events link-status software-interfaces
Admin config:
upgrade fpd all loc all
fpd auto-upgrade
Interface config:
interface name
ipv4 unreachable disable
ipv6 unreachable disable
dampening 1 xxx yyy 1
OSPF config:
router ospf xxx
graceful-restart
router ospfv3 xxx
graceful-restart
MPLS LDP:
mpls ldp neighbor <ip_address> password <pwd>’
AAA:
aaa authorization exec default group tacacs+ none
aaa authorization commands default group tacacs+ none
Monday, 6 May 2019
How to upgrade Field Programmable Device (FPD) on Cisco IOS XR
How to upgrade Field Programmable Device (FPD) on Cisco IOS XR
As per Cisco official documentation, the definition of FPD as follows:
An FPD refers to any programmable hardware device on a router, which includes a Field Programmable Gate Array (FPGA) and Read Only Memory Monitor (ROMMON). Cisco IOS® XR routers use a number of FPDs that are crucial for the function of route processors, line cards, shared port adapters (SPAs), SPA Interface Processors (SIPs), and fan trays.
1. Use the command 'show hw-module' to provide information about the FPD
Sample:
RP/0/RSP0/CPU0:CISCO-A9K#admin show hw-module fpd location all
===================================== ==========================================
Existing Field Programmable Devices
==========================================
HW Current SW Upg/
Location Card Type Version Type Subtype Inst Version Dng?
============ ======================== ======= ==== ======= ==== =========== ====
0/RSP0/CPU0 A9K-RSP880-TR 1.0 lc cbc 0 34.38 No
lc rommon 0 10.59 No
lc fpga2 0 0.57 No
lc fsbl 0 1.103 No
lc lnxfw 0 1.103 No
lc fpga3 0 0.16 No
lc fpga4 0 0.16 No
lc fpga5 0 0.12 No
lc fpga6 0 0.06 No
--------------------------------------------------------------------------------
0/FT0/SP ASR-9010-FAN-V2 1.0 ft cbc 7 29.12 No
--------------------------------------------------------------------------------
0/FT1/SP ASR-9010-FAN-V2 1.0 ft cbc 8 29.12 No
--------------------------------------------------------------------------------
0/BPID0/SP ASR-9010-BPID2 1.0 bp cbc 11 7.105 No
--------------------------------------------------------------------------------
0/PS0/M0/SP PWR-6KW-AC-V3 1.0 pm fpga11 13 4.03^ Yes
pm fpga12 13 4.01^ Yes
pm fpga13 13 4.02^ Yes
--------------------------------------------------------------------------------
0/PS0/M1/SP PWR-6KW-AC-V3 1.0 pm fpga11 14 4.03^ Yes
pm fpga12 14 4.01^ Yes
pm fpga13 14 4.02^ Yes
--------------------------------------------------------------------------------
0/PS1/M0/SP PWR-6KW-AC-V3 1.0 pm fpga11 17 4.03^ Yes
pm fpga12 17 4.01^ Yes
pm fpga13 17 4.02^ Yes
--------------------------------------------------------------------------------
0/PS1/M1/SP PWR-6KW-AC-V3 1.0 pm fpga11 18 4.03^ Yes
pm fpga12 18 4.01^ Yes
pm fpga13 18 4.02^ Yes
NOTES:
1. One or more FPD needs an upgrade. This can be accomplished
using the "admin> upgrade hw-module fpd <fpd> location <loc>" CLI.
2. ^ One or more FPD will be intentionally skipped from upgrade using CLI with option "all" or during "Auto fpd".
It can be upgraded only using the "admin> upgrade hw-module fpd <fpd> location <loc>" CLI with exact location.
Note: As you can see those FANs and RSPs no longer require upgrade as from the column Upg/Dng? are stated as "No", while those PWR-6KW power supply are stated as "Yes".
From the message above, it was mentioned that upgrade can be accomplished using the command
"admin> upgrade hw-module fpd <fpd> location <loc>"
It can be upgraded by using this command:
admin>upgrade hw-module fpd all location all
This is to upgrade all the fpd of all the linecards inserted in the router. But not always works as some fpd need to specify the location.
RP/0/RSP0/CPU0:CISCO-A9K(admin)#upgrade hw-module fpd all location all
This can take some time for a full chassis.
Ensure that system is not power cycled during the upgrades.
Please consult the documentation for more information.
***** UPGRADE WARNING MESSAGE: *****
* This upgrade operation has a maximum timout of 90 minutes. *
* If you are executing the cmd for one specific location and *
* card in that location reloads or goes down for some reason *
* you can press CTRL-C to get back the RP's prompt. *
* If you are executing the cmd for _all_ locations and a node *
* reloads or is down please allow other nodes to finish the *
* upgrade process before pressing CTRL-C. *
% RELOAD REMINDER:
- The upgrade operation of the target module will not interrupt its normal
operation. However, for the changes to take effect, the target module
will need to be manually reloaded after the upgrade operation. This can
be accomplished with the use of "hw-module <target> reload" command.
- If automatic reload operation is desired after the upgrade, please use
the "reload" option at the end of the upgrade command.
- The output of "show hw-module fpd location" command will not display
correct version information after the upgrade if the target module is
not reloaded.
NOTE: Chassis CLI will not be accessible while upgrade is in progress.
Continue ? [no]: yes
No fpd on location 0/RSP0/CPU0 need upgrade at this time.
No fpd on location 0/RSP1/CPU0 need upgrade at this time.
No fpd on location 0/0/CPU0 need upgrade at this time.
No fpd on location 0/1/CPU0 need upgrade at this time.
No fpd on location 0/2/CPU0 need upgrade at this time.
Example:
RP/0/RSP0/CPU0:CISCO-A9K(admin)#upgrade hw-module fpd all location 0/PS0/M1/SP
***** UPGRADE WARNING MESSAGE: *****
* This upgrade operation has a maximum timout of 90 minutes. *
* If you are executing the cmd for one specific location and *
* card in that location reloads or goes down for some reason *
* you can press CTRL-C to get back the RP's prompt. *
* If you are executing the cmd for _all_ locations and a node *
* reloads or is down please allow other nodes to finish the *
* upgrade process before pressing CTRL-C. *
% RELOAD REMINDER:
- The upgrade operation of the target module will not interrupt its normal
operation. However, for the changes to take effect, the target module
will need to be manually reloaded after the upgrade operation. This can
be accomplished with the use of "hw-module <target> reload" command.
- If automatic reload operation is desired after the upgrade, please use
the "reload" option at the end of the upgrade command.
- The output of "show hw-module fpd location" command will not display
correct version information after the upgrade if the target module is
not reloaded.
NOTE: Chassis CLI will not be accessible while upgrade is in progress.
Continue ? [no]: yes
FPD upgrade in progress on some hardware, reload/configuration change
on those is not recommended as it might cause HW programming failure
and result in RMA of the hardware.
Starting the upgrade/download of following FPDs:
=========== ==== ======= ======= =========== =========
Current Upg/Dng
Location Type Subtype Upg/Dng Version Version
=========== ==== ======= ======= =========== =========
0/PS0/M1/SP pm fpga11 upg 4.03 4.04
pm fpga12 upg 4.01 4.02
pm fpga13 upg 4.02 4.03
------------------------------------------------------
Upgrading Delta Power Module Firmware
0/PS0/M1/SP : module: Delta AC V3, upgrade supprted: Parallel
Current power supply 0/PS0/M1/SP firmware version: (Logic 4.3) (Secondary 4.2) (Primary 4.1)
Starting firmware upgrade of power supply 0/PS0/M1/SP Primary 54V micro-controller 0
File path = /net/node0_RSP0_CPU0/disk0:/asr9k-fpd-6.2.3.sp4-1.0.0/fpd/ucode/delta_v3_ac_primary_mcu.bin.gz, Image start 0x1800, No of pages = 64, No of blocks/page = 4, xmit_size = 64
Unzipping the file /net/node0_RSP0_CPU0/disk0:/asr9k-fpd-6.2.3.sp4-1.0.0/fpd/ucode/delta_v3_ac_primary_mcu.bin.gz
Unzipping of file /net/node0_RSP0_CPU0/disk1a:/fpd/delta_v3_ac_primary_mcu.bin.gz complete
FPD upgrade in progress. Max timeout remaining 89 min.
Upgraded power supply 0/PS0/M1/SP firmware version: (Logic 4.3) (Secondary 4.2) (Primary 4.2)
FPD upgrade in progress. Max timeout remaining 88 min.
Upgrading Delta Power Module Firmware
0/PS0/M1/SP : module: Delta AC V3, upgrade supprted: Serial
Current power supply 0/PS0/M1/SP firmware version: (Logic 4.3) (Secondary 4.2) (Primary 4.2)
Starting firmware upgrade of power supply 0/PS0/M1/SP Secondary 5V micro-controller 0
File path = /net/node0_RSP0_CPU0/disk0:/asr9k-fpd-6.2.3.sp4-1.0.0/fpd/ucode/delta_v3_ac_sec5v_mcu.bin.gz, Image start 0x2000, No of pages = 896, No of blocks/page = 1, xmit_size = 64
Unzipping the file /net/node0_RSP0_CPU0/disk0:/asr9k-fpd-6.2.3.sp4-1.0.0/fpd/ucode/delta_v3_ac_sec5v_mcu.bin.gz
Unzipping of file /net/node0_RSP0_CPU0/disk1a:/fpd/delta_v3_ac_sec5v_mcu.bin.gz complete
FPD upgrade in progress. Max timeout remaining 87 min.
FPD upgrade in progress. Max timeout remaining 86 min.
FPD upgrade in progress. Max timeout remaining 85 min.
Upgraded power supply 0/PS0/M1/SP firmware version: (Logic 4.4) (Secondary 4.2) (Primary 4.2)
Upgrading Delta Power Module Firmware
0/PS0/M1/SP : module: Delta AC V3, upgrade supprted: Parallel
Current power supply 0/PS0/M1/SP firmware version: (Logic 4.4) (Secondary 4.2) (Primary 4.2)
Starting firmware upgrade of power supply 0/PS0/M1/SP Secondary 54V micro-controller 0
File path = /net/node0_RSP0_CPU0/disk0:/asr9k-fpd-6.2.3.sp4-1.0.0/fpd/ucode/delta_v3_ac_sec54v_mcu.bin.gz, Image start 0x2000, No of pages = 640, No of blocks/page = 1, xmit_size = 64
Unzipping the file /net/node0_RSP0_CPU0/disk0:/asr9k-fpd-6.2.3.sp4-1.0.0/fpd/ucode/delta_v3_ac_sec54v_mcu.bin.gz
Unzipping of file /net/node0_RSP0_CPU0/disk1a:/fpd/delta_v3_ac_sec54v_mcu.bin.gz complete
FPD upgrade in progress. Max timeout remaining 84 min.
FPD upgrade in progress. Max timeout remaining 83 min.
FPD upgrade in progress. Max timeout remaining 82 min.
FPD upgrade in progress. Max timeout remaining 81 min.
FPD upgrade in progress. Max timeout remaining 80 min.
Upgraded power supply 0/PS0/M1/SP firmware version: (Logic 4.4) (Secondary 4.3) (Primary 4.2)
Successfully upgraded fpga11 for PWR-6KW-AC-V3 on location 0/PS0/M1/SP from 4.03 to 4.04
Successfully upgraded fpga12 for PWR-6KW-AC-V3 on location 0/PS0/M1/SP from 4.01 to 4.02
Successfully upgraded fpga13 for PWR-6KW-AC-V3 on location 0/PS0/M1/SP from 4.02 to 4.03
FPD upgrade has ended.
Saturday, 4 May 2019
Steps in Upgrading Cisco IOS-XR code
These are the steps in upgrading Cisco IOS-XR from 5.x.x to 6.x.x
1. Download from Cisco website the necessary files for the upgrade, usually images are in package installation envelope (.pie) format.
One way of transferring files to the router is via USB port, thus copy these files in your USB thumb drive and insert in USB port in your active RSP linecard.
2. Copy files from usb to harddisk.
RP/0/RSP0/CPU0:CISCO-A9K#dir usb:
Directory of usb:
131648 -rw- 23790534 Wed Jul 11 13:20:51 2018 asr9k-mpls-px.pie-6.x.x
131744 -rw- 4826385 Wed Jul 11 13:20:54 2018 asr9k-doc-px.pie-6.x.x
131840 -rw- 493632091 Wed Jul 11 13:24:28 2018 asr9k-fpd-px.pie-6.x.x
131936 -rw- 27112275 Wed Jul 11 13:24:45 2018 asr9k-k9sec-px.pie-6.x.x
132032 -rw- 38070588 Wed Jul 11 13:25:05 2018 asr9k-mgbl-px.pie-6.x.x
132128 -rw- 487071236 Wed Jul 11 13:20:36 2018 asr9k-mini-px.pie-6.x.x
RP/0/RSP0/CPU0:CISCO-A9K#copy usb:/harddisk:/asr9k-mpls-px.pie-6.x.x harddisk:
Destination filename [/harddisk:/asr9k-mpls-px.pie-6.x.x]?
CCCCCCCCCCCCCCCCCCCCCCC
23790534 bytes copied in 2 sec ( 9111656)bytes/sec
RP/0/RSP0/CPU0:CISCO-A9K#copy usb:/asr9k-doc-px.pie-6.x.x harddisk:
Destination filename [/harddisk:/asr9k-doc-px.pie-6.x.x]?
CCCCC
4826385 bytes copied in 0 sec
RP/0/RSP0/CPU0:CISCO-A9K#copy usb:/asr9k-fpd-px.pie-6.x.x harddisk:
Destination filename [/harddisk:/asr9k-fpd-px.pie-6.x.x]?
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
493632091 bytes copied in 54 sec ( 9014135)bytes/sec
RP/0/RSP0/CPU0:CISCO-A9K#copy usb:/asr9k-k9sec-px.pie-6.x.x harddisk:
Destination filename [/harddisk:/asr9k-k9sec-px.pie-6.x.x]?
CCCCCCCCCCCCCCCCCCCCCCCCCC
27112275 bytes copied in 3 sec ( 8240813)bytes/sec
RP/0/RSP0/CPU0:CISCO-A9K#copy usb:/asr9k-mgbl-px.pie-6.x.x harddisk:
Destination filename [/harddisk:/asr9k-mgbl-px.pie-6.x.x]?
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
38070588 bytes copied in 4 sec ( 8258262)bytes/sec
RP/0/RSP0/CPU0:CISCO-A9K#copy usb:/asr9k-mini-px.pie-6.x.x harddisk:
Destination filename [/harddisk:/asr9k-mini-px.pie-6.x.x]?
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
487071236 bytes copied in 62 sec ( 7826449)bytes/sec
3. Verify the files if copied successfully and compare the file sizes if the same.
RP/0/RSP0/CPU0:CISCO-A9K#dir harddisk:*6.x.x*
Directory of harddisk:
25064 -rw- 23790534 Thu May 2 09:25:03 2019 asr9k-mpls-px.pie-6.x.x
25065 -rw- 4826385 Thu May 2 09:25:21 2019 asr9k-doc-px.pie-6.x.x
25066 -rw- 493632091 Thu May 2 09:26:24 2019 asr9k-fpd-px.pie-6.x.x
25067 -rw- 27112275 Thu May 2 09:27:35 2019 asr9k-k9sec-px.pie-6.x.x
25068 -rw- 38070588 Thu May 2 09:27:50 2019 asr9k-mgbl-px.pie-6.x.x
25069 -rw- 487071236 Thu May 2 09:29:03 2019 asr9k-mini-px.pie-6.x.x
4. Add the packages for activation later on
RP/0/RSP0/CPU0:CISCO-A9K#admin install add harddisk:/asr9k-mpls-px.pie-6.x.x harddisk:/asr9k-doc-px.pie-6.x.x harddisk:/asr9k-fpd-px.pie-6.x.x harddisk:/asr9k-k9sec-px.pie-6.x.x harddisk:/asr9k-mgbl-px.pie-6.x.x harddisk:/asr9k-mini-px.pie-6.x.x harddisk:/asr9k-px-6.x.x.k9-sp4.pie synchronous
Install operation 15 '(admin) install add /harddisk:/asr9k-mpls-px.pie-6.x.x /harddisk:/asr9k-doc-px.pie-6.x.x /harddisk:/asr9k-fpd-px.pie-6.x.x /harddisk:/asr9k-k9sec-px.pie-6.x.x
/harddisk:/asr9k-mgbl-px.pie-6.x.x /harddisk:/asr9k-mini-px.pie-6.x.x synchronous' started by user 'admin' via CLI .
/ 1% complete:
Info: disk0:asr9k-mpls-px-6.x.x
Info: disk0:asr9k-doc-px-6.x.x
Info: disk0:asr9k-fpd-px-6.x.x
Info: disk0:asr9k-k9sec-px-6.x.x
Info: disk0:asr9k-mgbl-px-6.x.x
Info: disk0:asr9k-mini-px-6.x.x
Info:
Info: The packages can be activated across the entire router.
Info:
/ 100% complete: The operation can no longer be aborted (ctrl-c for options)
Install operation 15 completed successfully at 01:52:39 SGP Mon Apr 29 2019.
5. Verify the packages, it will be in the Inactive Packages list if added successfully.
RP/0/RSP0/CPU0:CISCO-A9K#admin show install inactive summary
Mon Apr 29 01:53:36.445 SGP
Default Profile:
SDRs:
Owner
Inactive Packages:
disk0:asr9k-mpls-px-6.x.x
disk0:asr9k-doc-px-6.x.x
disk0:asr9k-fpd-px-6.x.x
disk0:asr9k-k9sec-px-6.x.x
disk0:asr9k-mgbl-px-6.x.x
disk0:asr9k-mini-px-6.x.x
6. Activate the packages. Take note that this will reload the router after the installation. You can use wildcard to install all 6.x.x packages so no need to specify one by one
RP/0/RSP0/CPU0:CISCO-A9K#admin install activate disk0:*6.x.x* synchronous
Install operation 21 '(admin) install activate disk0:asr9k-mpls-px-6.x.x disk0:asr9k-doc-px-6.x.x disk0:asr9k-fpd-px-6.x.x disk0:asr9k-k9sec-px-6.x.x disk0:asr9k-mgbl-px-6.x.x disk0:asr9k-mini-px-6.x.x synchronous' started by user 'admin' via CLI at 04:19:03 SGP Mon Apr 29 2019.
/ 1% complete: The operation can still be aborted (ctrl-c for options)
7. Install commit to commit the active software
Logs:
%INSTALL-INSTMGR-4-ACTIVE_SOFTWARE_COMMITTED_INFO : The currently active software is not committed. If the system reboots then the committed software will be used. Use 'install commit' to commit the active software.
RP/0/RSP0/CPU0:CISCO-A9K#admin install commit
Mon Apr 29 04:31:40.468 SGP
Install operation 22 '(admin) install commit' started by user 'admin' via CLI at
04:31:40 SGP Mon Apr 29 2019.
/ 20% complete: The operation can no longer be aborted (ctrl-c for options
Install operation 22 completed successfully at 04:31:51 SGP Mon Apr 29 2019.
8.Verify if the new code is committed successfully
RP/0/RSP0/CPU0:CISCO-A9K#admin show install committed summary
Mon Apr 29 04:32:04.140 SGP
Default Profile:
SDRs:
Owner
Committed Packages:
disk0:asr9k-mpls-px-6.x.x
disk0:asr9k-doc-px-6.x.x
disk0:asr9k-fpd-px-6.x.x
disk0:asr9k-k9sec-px-6.x.x
disk0:asr9k-mgbl-px-6.x.x
disk0:asr9k-mini-px-6.x.x
Thursday, 2 May 2019
GNS3 setup
GNS3 setup
My old school multi-platform setup. Cisco IOS 7200 ver.15 + juniper 12.1R9 (JunOS Olive) + Cisco IOS XRv 5.1.1 running in MacOS + GNS3
This is the setup I did to practice on my RPL for IOS-XR which unfortunately that time we still don't have the lab environment.
My old school multi-platform setup. Cisco IOS 7200 ver.15 + juniper 12.1R9 (JunOS Olive) + Cisco IOS XRv 5.1.1 running in MacOS + GNS3
This is the setup I did to practice on my RPL for IOS-XR which unfortunately that time we still don't have the lab environment.
Installation Files needed for IOS-XR
Installation Files needed for IOS-XR
The required files can only be downloaded via Cisco official website and needs an authorized account. Just go to 'Software Download' and search for the product name. Select for the software types, sample as follows:
IOS XR Service Packs
IOS XR Software (this is where you can download main packages)
IOS XR Software Maintenance Upgrades (SMU)
IOS XR Software Maintenance Upgrades (SMU) Bundles
The files needed depend on user or organization requirements, services offered and features that they wanted to run.
For basic installation, these are the following installation files needed . Main packages as follow:
Composite Package:
Filename:asr9k-mini-px.pie-x.x.x
Feature Set: Cisco IOS XR IP Unicast Routing Core Bundle
Description: Contains the required core packages, including OS, Admin, Base, Forwarding, Modular Services Card, Routing, SNMP Agent, and Alarm Correlation.
The mini pie file is used for upgrading to the new release
Optional Packages:
Filename:asr9k-mgbl-px.pie-x.x.x
Feature Set: Cisco IOS XR Manageability Package
Description:CORBA2 agent, XML3 Parser, and HTTP server packages. This PIE also contains some SNMP MIB infrastructure. Certain MIBs won't work if this PIE is not installed.
IPSLA and environment MIBs are part of the mgbl pie.
Filename:asr9k-fpd-px.pie-x.x.x
Feature Set: Cisco IOS XR FPD Package
Description:Firmware pie for all LC and RSP FPGAs and ASICs.
Filename:asr9k-k9sec-px.pie-x.x.x
Feature Set: Cisco IOS XR Security Package
Description:Support for Encryption, Decryption, IP Security (IPSec), Secure Shell (SSH), Secure Socket Layer (SSL), and Public-key infrastructure (PKI) (IPSec is supported only for OSPFv3).
Filename:asr9k-mpls-px.pie-x.x.x
Feature Set: Cisco IOS XR MPLS Package
Description:MPLS Traffic Engineering (MPLS-TE), Label Distribution Protocol (LDP), MPLS Forwarding, MPLS Operations, Administration, and Maintenance (OAM), Link Manager Protocol (LMP), Optical User Network Interface (OUNI), Resource Reservation Protocol (RSVP), and Layer-3 VPN.
Filename:asr9k-doc-px.pie-x.x.x
Feature Set: Cisco IOS XR Documentation Package
Description:.man pages for Cisco IOS XR Software on the Cisco ASR 9000 Series Aggregation Services Router Chassis.
You can download necessary SMUs as per your vendor's recommendation, else download the latest Service packs that will include all those patches or bug fixes.
asr9k-px-x.x.x.k9-sp1
After installation, you should the following packages activated and committed in the router:
RP/0/RSP0/CPU0:ios-xr#show install active summary
Default Profile:
SDRs:
Owner
Active Packages:
disk0:asr9k-mini-px-x.x.x
disk0:asr9k-doc-px-x.x.x
disk0:asr9k-fpd-px-x.x.x
disk0:asr9k-k9sec-px-x.x.x
disk0:asr9k-mgbl-px-x.x.x
disk0:asr9k-mpls-px-x.x.x
disk0:asr9k-px-x.x.x.spx-1.0.0
RP/0/RSP0/CPU0:ios-xr#show install committed summary
Default Profile:
SDRs:
Owner
Committed Packages:
disk0:asr9k-mini-px-x.x.x
disk0:asr9k-doc-px-x.x.x
disk0:asr9k-fpd-px-x.x.x
disk0:asr9k-k9sec-px-x.x.x
disk0:asr9k-mgbl-px-x.x.x
disk0:asr9k-mpls-px-x.x.x
disk0:asr9k-px-x.x.x.spx-1.0.0
The required files can only be downloaded via Cisco official website and needs an authorized account. Just go to 'Software Download' and search for the product name. Select for the software types, sample as follows:
IOS XR Service Packs
IOS XR Software (this is where you can download main packages)
IOS XR Software Maintenance Upgrades (SMU)
IOS XR Software Maintenance Upgrades (SMU) Bundles
The files needed depend on user or organization requirements, services offered and features that they wanted to run.
For basic installation, these are the following installation files needed . Main packages as follow:
Composite Package:
Filename:asr9k-mini-px.pie-x.x.x
Feature Set: Cisco IOS XR IP Unicast Routing Core Bundle
Description: Contains the required core packages, including OS, Admin, Base, Forwarding, Modular Services Card, Routing, SNMP Agent, and Alarm Correlation.
The mini pie file is used for upgrading to the new release
Optional Packages:
Filename:asr9k-mgbl-px.pie-x.x.x
Feature Set: Cisco IOS XR Manageability Package
Description:CORBA2 agent, XML3 Parser, and HTTP server packages. This PIE also contains some SNMP MIB infrastructure. Certain MIBs won't work if this PIE is not installed.
IPSLA and environment MIBs are part of the mgbl pie.
Filename:asr9k-fpd-px.pie-x.x.x
Feature Set: Cisco IOS XR FPD Package
Description:Firmware pie for all LC and RSP FPGAs and ASICs.
Filename:asr9k-k9sec-px.pie-x.x.x
Feature Set: Cisco IOS XR Security Package
Description:Support for Encryption, Decryption, IP Security (IPSec), Secure Shell (SSH), Secure Socket Layer (SSL), and Public-key infrastructure (PKI) (IPSec is supported only for OSPFv3).
Filename:asr9k-mpls-px.pie-x.x.x
Feature Set: Cisco IOS XR MPLS Package
Description:MPLS Traffic Engineering (MPLS-TE), Label Distribution Protocol (LDP), MPLS Forwarding, MPLS Operations, Administration, and Maintenance (OAM), Link Manager Protocol (LMP), Optical User Network Interface (OUNI), Resource Reservation Protocol (RSVP), and Layer-3 VPN.
Filename:asr9k-doc-px.pie-x.x.x
Feature Set: Cisco IOS XR Documentation Package
Description:.man pages for Cisco IOS XR Software on the Cisco ASR 9000 Series Aggregation Services Router Chassis.
You can download necessary SMUs as per your vendor's recommendation, else download the latest Service packs that will include all those patches or bug fixes.
asr9k-px-x.x.x.k9-sp1
After installation, you should the following packages activated and committed in the router:
RP/0/RSP0/CPU0:ios-xr#show install active summary
Default Profile:
SDRs:
Owner
Active Packages:
disk0:asr9k-mini-px-x.x.x
disk0:asr9k-doc-px-x.x.x
disk0:asr9k-fpd-px-x.x.x
disk0:asr9k-k9sec-px-x.x.x
disk0:asr9k-mgbl-px-x.x.x
disk0:asr9k-mpls-px-x.x.x
disk0:asr9k-px-x.x.x.spx-1.0.0
RP/0/RSP0/CPU0:ios-xr#show install committed summary
Default Profile:
SDRs:
Owner
Committed Packages:
disk0:asr9k-mini-px-x.x.x
disk0:asr9k-doc-px-x.x.x
disk0:asr9k-fpd-px-x.x.x
disk0:asr9k-k9sec-px-x.x.x
disk0:asr9k-mgbl-px-x.x.x
disk0:asr9k-mpls-px-x.x.x
disk0:asr9k-px-x.x.x.spx-1.0.0
Configuration Inconsistency and Errors Verification in Cisco ASR9000
Configuration Inconsistency and Errors Verification in Cisco ASR9000
RP/0/RSP0/CPU0:ASR9K-ROUTER#show redundancy
Thu Feb 14 03:06:44.176 UTC
Redundancy information for node 0/RSP0/CPU0:
==========================================
Node 0/RSP0/CPU0 is in ACTIVE role
Node Redundancy Partner (0/RSP1/CPU0) is in STANDBY role
Standby node in 0/RSP1/CPU0 is ready
Standby node in 0/RSP1/CPU0 is NSR-ready
Node 0/RSP0/CPU0 is in process group PRIMARY role
Process Redundancy Partner (0/RSP1/CPU0) is in BACKUP role
Backup node in 0/RSP1/CPU0 is ready
Backup node in 0/RSP1/CPU0 is NSR-ready
Group Primary Backup Status
--------- --------- --------- ---------
dsc 0/RSP0/CPU0 0/RSP1/CPU0 Ready
dlrsc 0/RSP0/CPU0 0/RSP1/CPU0 Ready
central-services 0/RSP0/CPU0 0/RSP1/CPU0 Ready
v4-routing 0/RSP0/CPU0 0/RSP1/CPU0 Ready
netmgmt 0/RSP0/CPU0 0/RSP1/CPU0 Ready
mcast-routing 0/RSP0/CPU0 0/RSP1/CPU0 Ready
v6-routing 0/RSP0/CPU0 0/RSP1/CPU0 Ready
Reload and boot info
----------------------
A9K-RSP-4G reloaded Thu Feb 7 07:55:47 2019: 6 days, 19 hours, 10 minutes ago
Active node booted Thu Feb 7 07:55:47 2019: 6 days, 19 hours, 10 minutes ago
Standby node boot Thu Feb 7 07:53:44 2019: 6 days, 19 hours, 13 minutes ago
Standby node last went not ready Thu Feb 7 08:03:59 2019: 6 days, 19 hours, 2 minutes ago
Standby node last went ready Thu Feb 7 08:04:00 2019: 6 days, 19 hours, 2 minutes ago
There have been 0 switch-overs since reload
Active node reload "Cause: Node 0/RSP1/CPU0 is in STANDBY role and is not ready"
Standby node reload "Cause: dSC node reload is required by install operation"
RP/0/RSP0/CPU0:ASR9K-ROUTER#show configuration inconsistency replica location 0/RSP1/CPU0
Thu Feb 14 03:07:18.182 UTC
The replica at location 0/RSP1/CPU0 is inconsistent. Please run 'clear configuration inconsistency replica location 0/RSP1/CPU0'.
RP/0/RSP0/CPU0:ASR9K-ROUTER#clear configuration inconsistency replica location 0/RSP1/CPU0
Thu Feb 14 03:07:42.120 UTC
The replica has been repaired.
RP/0/RSP0/CPU0:ASR9K-ROUTER#show configuration inconsistency replica location 0/RSP1/CPU0
Thu Feb 14 03:08:06.539 UTC
Replica is consistent
RP/0/RSP0/CPU0:ASR9K-ROUTER#cfs ?
check Check/fix the configuration file system
RP/0/RSP0/CPU0:ASR9K-ROUTER#cfs check
Thu Feb 14 03:09:06.264 UTC
Creating any missing directories in Configuration File system...OK
Initializing Configuration Version Manager...OK
Syncing commit database with running configuration...OK
RP/0/RSP0/CPU0:ASR9K-ROUTER#show redundancy
Thu Feb 14 03:06:44.176 UTC
Redundancy information for node 0/RSP0/CPU0:
==========================================
Node 0/RSP0/CPU0 is in ACTIVE role
Node Redundancy Partner (0/RSP1/CPU0) is in STANDBY role
Standby node in 0/RSP1/CPU0 is ready
Standby node in 0/RSP1/CPU0 is NSR-ready
Node 0/RSP0/CPU0 is in process group PRIMARY role
Process Redundancy Partner (0/RSP1/CPU0) is in BACKUP role
Backup node in 0/RSP1/CPU0 is ready
Backup node in 0/RSP1/CPU0 is NSR-ready
Group Primary Backup Status
--------- --------- --------- ---------
dsc 0/RSP0/CPU0 0/RSP1/CPU0 Ready
dlrsc 0/RSP0/CPU0 0/RSP1/CPU0 Ready
central-services 0/RSP0/CPU0 0/RSP1/CPU0 Ready
v4-routing 0/RSP0/CPU0 0/RSP1/CPU0 Ready
netmgmt 0/RSP0/CPU0 0/RSP1/CPU0 Ready
mcast-routing 0/RSP0/CPU0 0/RSP1/CPU0 Ready
v6-routing 0/RSP0/CPU0 0/RSP1/CPU0 Ready
Reload and boot info
----------------------
A9K-RSP-4G reloaded Thu Feb 7 07:55:47 2019: 6 days, 19 hours, 10 minutes ago
Active node booted Thu Feb 7 07:55:47 2019: 6 days, 19 hours, 10 minutes ago
Standby node boot Thu Feb 7 07:53:44 2019: 6 days, 19 hours, 13 minutes ago
Standby node last went not ready Thu Feb 7 08:03:59 2019: 6 days, 19 hours, 2 minutes ago
Standby node last went ready Thu Feb 7 08:04:00 2019: 6 days, 19 hours, 2 minutes ago
There have been 0 switch-overs since reload
Active node reload "Cause: Node 0/RSP1/CPU0 is in STANDBY role and is not ready"
Standby node reload "Cause: dSC node reload is required by install operation"
RP/0/RSP0/CPU0:ASR9K-ROUTER#show configuration inconsistency replica location 0/RSP1/CPU0
Thu Feb 14 03:07:18.182 UTC
The replica at location 0/RSP1/CPU0 is inconsistent. Please run 'clear configuration inconsistency replica location 0/RSP1/CPU0'.
RP/0/RSP0/CPU0:ASR9K-ROUTER#clear configuration inconsistency replica location 0/RSP1/CPU0
Thu Feb 14 03:07:42.120 UTC
The replica has been repaired.
RP/0/RSP0/CPU0:ASR9K-ROUTER#show configuration inconsistency replica location 0/RSP1/CPU0
Thu Feb 14 03:08:06.539 UTC
Replica is consistent
RP/0/RSP0/CPU0:ASR9K-ROUTER#cfs ?
check Check/fix the configuration file system
RP/0/RSP0/CPU0:ASR9K-ROUTER#cfs check
Thu Feb 14 03:09:06.264 UTC
Creating any missing directories in Configuration File system...OK
Initializing Configuration Version Manager...OK
Syncing commit database with running configuration...OK
Cisco IOS-XR Minimum System Requirements for Upgrade
Cisco IOS-XR Minimum System Requirements for Upgrade
For upgrading IOS-XR devices like ASR9000 routers, e.g. from 5.x to 6.x , the minimum memory requirements for ver. 6.2.3 are:
-minimum 2 GB compact flash on RSPs or Route Switch Processors
-minimum 6 GB memory on the RSP-440 and RP (ASR99xx)
-minimum 4 GB memory on LCs or Line Cards
Command that can be used to find the physical memory of each modules:
show watchdog memory-state location all | include "node|Physical Memory:"
Command that can be used to find the space of compact disk in active and Standby RSPs:
show filesystem disk0: location 0/RSP0/CPU0
For upgrading IOS-XR devices like ASR9000 routers, e.g. from 5.x to 6.x , the minimum memory requirements for ver. 6.2.3 are:
-minimum 2 GB compact flash on RSPs or Route Switch Processors
-minimum 6 GB memory on the RSP-440 and RP (ASR99xx)
-minimum 4 GB memory on LCs or Line Cards
Command that can be used to find the physical memory of each modules:
show watchdog memory-state location all | include "node|Physical Memory:"
Command that can be used to find the space of compact disk in active and Standby RSPs:
show filesystem disk0: location 0/RSP0/CPU0
Checking TX / RX optical power for Cisco IOS, IOS-XR, NX-OS & JunOS
Checking TX / RX optical power for Cisco IOS, IOS-XR, NX-OS & JunOS
For checking transmission links, it is good to know how to find out the optical power for troubleshooting and making sure the desired or optimal range is meet. Here are the sample commands for checking the TX/RX optical power.
IOS / IOS-XE
If want to check TX & RX power for IOS based devices such as ASR1K ,e.g. interface GigabitEthernet 0/2/2,here's how to do it:
IOS-router#show hw-module subslot 0/2 transceiver 2 status
The Transceiver in slot 0 subslot 2 port 2 is enabled.
Module temperature = +25.335 C
Transceiver Tx supply voltage = 3209.6 mVolts
Transceiver Tx bias current = 9704 uAmps
Transceiver Tx power = 3.2 dBm
Transceiver Rx optical power = -5.3 dBm
IOS-XR (CRS)
RP/0/RP1/CPU0:IOS-XR-CRS#show controllers Te0/0/0/1 phy
XFP Detail Info:
================
Temp: 29.53
Tx bias: 27.166 mA
Tx power: 0.5140 mW ( -2.9 dBm)
Rx power: 0.2402 mW ( -6.2 dBm)
AUX 1: +3.3V Supply Voltage: 0x70
AUX 2: Auxiliary monitoring not implemented: 0x0
IOS-XR (ASR9K) (10GE)
RP/0/RSP0/CPU0:IOS-XR-ASR9k#show controllers Te0/3/0/1 phy
Signal Condition Control: Normal Async REFCLK,
Thresholds: Alarm High Warning High Warning Low Alarm Low
Temperature: 78.000 73.000 5.000 0.000
Voltage: 0.000 Volt 0.000 Volt 0.000 Volt 0.000 Volt
Bias: 100.000 mAmps 85.000 mAmps 15.000 mAmps 5.000 mAmps
Transmit Power: 2.23870 mW (3.49996 dBm) 1.12200 mW (0.49993 dBm) 0.15130 mW (-8.20161 dBm) 0.07580 mW (-11.20331 dBm)
Receive Power: 2.23870 mW (3.49996 dBm) 1.12200 mW (0.49993 dBm) 0.03630 mW (-14.40093 dBm) 0.01810 mW (-17.42321 dBm)
Temperature: 31.402
Voltage: 0.000 Volt
Tx Bias: 40.820 mAmps
Tx Power: 0.65210 mW (-1.85686 dBm)
Rx Power: 0.51510 mW (-2.88108 dBm)
IOS-XR (ASR9K) (100GE)
RP/0/RSP0/CPU0:IOS-XR-ASR9K#show controllers Hu0/2/0/1 phy
Module
Thresholds: Alarm High Warning High Warning Low Alarm Low
Temperature: +80.000 C +75.000 C +0.000 C -5.000 C
Voltage: 3.663 Volt 3.531 Volt 3.069 Volt 2.937 Volt
Temperature: +36.835 C
Voltage: 3.264 Volt
Lanes
Thresholds: Alarm High Warning High Warning Low Alarm Low
Temperature: +62.507 C +60.507 C +54.507 C +52.507 C
Bias: 103.284 mAmps 98.284 mAmps 57.364 mAmps 52.364 mAmps
Transmit Power: 5.62000 mW (7.49736 dBm) 2.81000 mW (4.48706 dBm) 0.37000 mW (-4.31798 dBm) 0.14000 mW (-8.53872 dBm)
Receive Power: 5.62340 mW (7.49999 dBm) 2.81830 mW (4.49987 dBm) 0.08710 mW (-10.59982 dBm) 0.03470 mW (-14.59671 dBm)
Lane Temp Bias Tx Power Rx Power
0 +57.445 C 70.698 mAmps 0.78430 mW (-1.05518 dBm) 0.97850 mW (-0.09439 dBm)
1 +57.445 C 78.086 mAmps 0.74750 mW (-1.26389 dBm) 0.97000 mW (-0.13228 dBm)
2 +57.445 C 80.746 mAmps 0.75820 mW (-1.20216 dBm) 1.01760 mW (0.07577 dBm)
3 +57.445 C 78.684 mAmps 0.75790 mW (-1.20388 dBm) 1.09110 mW (0.37865 dBm)
CISCO NEXUS OS
N7K-SWITCH# show interface Eth1/1 transceiver details
SFP Detail Diagnostics Information (internal calibration)
----------------------------------------------------------------------------
Current Alarms Warnings
Measurement High Low High Low
----------------------------------------------------------------------------
Temperature 46.10 C 75.00 C -5.00 C 70.00 C 0.00 C
Voltage 3.34 V 3.63 V 2.97 V 3.46 V 3.13 V
Current 31.12 mA 70.00 mA 1.00 mA 68.00 mA 2.00 mA
Tx Power -0.42 dBm 3.49 dBm -12.19 dBm 0.49 dBm -8.19 dBm
Rx Power -3.87 dBm 3.49 dBm -18.38 dBm 0.49 dBm -14.40 dBm
Transmit Fault Count = 0
----------------------------------------------------------------------------
Note: ++ high-alarm; + high-warning; -- low-alarm; - low-warning
Juniper (MX)
darwin@JUNOS-RE0$ show interfaces diagnostics optics xe-0/0/0
Physical interface: xe-0/0/0
Laser bias current : 85.674 mA
Laser output power : 1.5530 mW / 1.91 dBm
Module temperature : 45 degrees C / 112 degrees F
Module voltage : 3.2980 V
Receiver signal average optical power : 0.0181 mW / -17.42 dBm
For checking transmission links, it is good to know how to find out the optical power for troubleshooting and making sure the desired or optimal range is meet. Here are the sample commands for checking the TX/RX optical power.
IOS / IOS-XE
If want to check TX & RX power for IOS based devices such as ASR1K ,e.g. interface GigabitEthernet 0/2/2,here's how to do it:
IOS-router#show hw-module subslot 0/2 transceiver 2 status
The Transceiver in slot 0 subslot 2 port 2 is enabled.
Module temperature = +25.335 C
Transceiver Tx supply voltage = 3209.6 mVolts
Transceiver Tx bias current = 9704 uAmps
Transceiver Tx power = 3.2 dBm
Transceiver Rx optical power = -5.3 dBm
IOS-XR (CRS)
RP/0/RP1/CPU0:IOS-XR-CRS#show controllers Te0/0/0/1 phy
XFP Detail Info:
================
Temp: 29.53
Tx bias: 27.166 mA
Tx power: 0.5140 mW ( -2.9 dBm)
Rx power: 0.2402 mW ( -6.2 dBm)
AUX 1: +3.3V Supply Voltage: 0x70
AUX 2: Auxiliary monitoring not implemented: 0x0
IOS-XR (ASR9K) (10GE)
RP/0/RSP0/CPU0:IOS-XR-ASR9k#show controllers Te0/3/0/1 phy
Signal Condition Control: Normal Async REFCLK,
Thresholds: Alarm High Warning High Warning Low Alarm Low
Temperature: 78.000 73.000 5.000 0.000
Voltage: 0.000 Volt 0.000 Volt 0.000 Volt 0.000 Volt
Bias: 100.000 mAmps 85.000 mAmps 15.000 mAmps 5.000 mAmps
Transmit Power: 2.23870 mW (3.49996 dBm) 1.12200 mW (0.49993 dBm) 0.15130 mW (-8.20161 dBm) 0.07580 mW (-11.20331 dBm)
Receive Power: 2.23870 mW (3.49996 dBm) 1.12200 mW (0.49993 dBm) 0.03630 mW (-14.40093 dBm) 0.01810 mW (-17.42321 dBm)
Temperature: 31.402
Voltage: 0.000 Volt
Tx Bias: 40.820 mAmps
Tx Power: 0.65210 mW (-1.85686 dBm)
Rx Power: 0.51510 mW (-2.88108 dBm)
IOS-XR (ASR9K) (100GE)
RP/0/RSP0/CPU0:IOS-XR-ASR9K#show controllers Hu0/2/0/1 phy
Module
Thresholds: Alarm High Warning High Warning Low Alarm Low
Temperature: +80.000 C +75.000 C +0.000 C -5.000 C
Voltage: 3.663 Volt 3.531 Volt 3.069 Volt 2.937 Volt
Temperature: +36.835 C
Voltage: 3.264 Volt
Lanes
Thresholds: Alarm High Warning High Warning Low Alarm Low
Temperature: +62.507 C +60.507 C +54.507 C +52.507 C
Bias: 103.284 mAmps 98.284 mAmps 57.364 mAmps 52.364 mAmps
Transmit Power: 5.62000 mW (7.49736 dBm) 2.81000 mW (4.48706 dBm) 0.37000 mW (-4.31798 dBm) 0.14000 mW (-8.53872 dBm)
Receive Power: 5.62340 mW (7.49999 dBm) 2.81830 mW (4.49987 dBm) 0.08710 mW (-10.59982 dBm) 0.03470 mW (-14.59671 dBm)
Lane Temp Bias Tx Power Rx Power
0 +57.445 C 70.698 mAmps 0.78430 mW (-1.05518 dBm) 0.97850 mW (-0.09439 dBm)
1 +57.445 C 78.086 mAmps 0.74750 mW (-1.26389 dBm) 0.97000 mW (-0.13228 dBm)
2 +57.445 C 80.746 mAmps 0.75820 mW (-1.20216 dBm) 1.01760 mW (0.07577 dBm)
3 +57.445 C 78.684 mAmps 0.75790 mW (-1.20388 dBm) 1.09110 mW (0.37865 dBm)
CISCO NEXUS OS
N7K-SWITCH# show interface Eth1/1 transceiver details
SFP Detail Diagnostics Information (internal calibration)
----------------------------------------------------------------------------
Current Alarms Warnings
Measurement High Low High Low
----------------------------------------------------------------------------
Temperature 46.10 C 75.00 C -5.00 C 70.00 C 0.00 C
Voltage 3.34 V 3.63 V 2.97 V 3.46 V 3.13 V
Current 31.12 mA 70.00 mA 1.00 mA 68.00 mA 2.00 mA
Tx Power -0.42 dBm 3.49 dBm -12.19 dBm 0.49 dBm -8.19 dBm
Rx Power -3.87 dBm 3.49 dBm -18.38 dBm 0.49 dBm -14.40 dBm
Transmit Fault Count = 0
----------------------------------------------------------------------------
Note: ++ high-alarm; + high-warning; -- low-alarm; - low-warning
Juniper (MX)
darwin@JUNOS-RE0$ show interfaces diagnostics optics xe-0/0/0
Physical interface: xe-0/0/0
Laser bias current : 85.674 mA
Laser output power : 1.5530 mW / 1.91 dBm
Module temperature : 45 degrees C / 112 degrees F
Module voltage : 3.2980 V
Receiver signal average optical power : 0.0181 mW / -17.42 dBm
IOS-XR Pre & Post Upgrade / Installation Commands
| These are the some commands being used when performing network change or maintenance, depending on the features or services being run in the network. Typically, this is very useful in verification, troubleshooting and comparison between before and after the change. terminal exec prompt timestamp |
| terminal length 0 |
| show version |
| show run |
| show filesystem location 0/rsp0/cpu0 |
| show filesystem location 0/rsp1/cpu0 |
| show ipv4 interface brief |
| show ipv6 interface brief show route ipv4 summary show route ipv6 summary show route vrf all ipv4 summary show route vrf all ipv6 summary show dhcp ipv6 proxy binding summary |
| show ospf interface brief |
| show ospf neighbor |
| show bgp all all summary |
| show mpls ldp discovery |
| show mpls ldp interface brief |
| show mpls ldp neighbor brief |
show isis neighbors
show isis interface brief
show bgp all all summary
show mpls ldp discovery
show mpls ldp interface brief
show mpls ldp neighbor brief
show rsvp interface
show mpls traffic-eng topology summary
show mpls traffic-eng pce lsp-database
show mpls traffic-eng pce peer all
show l2vpn bridge-domain summary
show l2vpn forwarding bridge-domain mac-address summary location 0/0/cpU0
show iccp group
show bundle
show watchdog memory-state location all | in Memory State:
show cef resource | exclude GREEN
show controllers fabric fia link-status
show mpls ldp neighbor
show mpls traffic-eng topology
show bgp all all neighbors detail
show l2vpn bridge-domain detail
show l2vpn forwarding bridge-domain mac-address location 0/0/cpU0
show controllers np counters all
show install events
show drops
From Full-time SysAd to Network Engineer
I created this blog to document those stuffs that I learned and experience as a Network Engineer.
Subscribe to:
Posts (Atom)
-
Taking Cisco's Sample Legal Banner message from their Network Security Baseline page. Sample Legal Banner Notification Configuration !... -
Assumption: JunOS is downloaded and stored in an FTP server. Step1: Download the necessary image from the FTP server. Save it in the /var/tm...
-
Objective: To separate management traffic from data/customer traffic in your Cisco XR routers. Preferably, Data and Management are into 2...