Reference
This guide describes the commands supported in Cisco NCS 1004. For information on Cisco IOS XR commands, see here.
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This guide describes the commands supported in Cisco NCS 1004. For information on Cisco IOS XR commands, see here.
To configure authentication, authorization, and accounting (AAA) authentication at login, use the aaa authentication login command in global configuration mode.
aaa authentication login { default | list-name } method-list
| login | Sets authentication for login. |
| default |
Uses the listed authentication methods that follow this keyword as the default list of methods for authentication. |
|
list-name |
Character string used to name the authentication method list. |
|
method-list |
Method used to enable AAA system accounting. Method list types are entered in the preferred sequence. The value is one of the following options:
|
No authentication is performed.
Global configuration
| Release | Modification |
|---|---|
| R7.0.1 |
This command was introduced. |
The following example shows how to specify the default method list for authentication, and also enable authentication.
configure
aaa authentication login default group tacacs+
exit
commit
To create a method list for authorization, use the aaa authorization command in global configuration mode.
aaa authorization {exec | nacm} { default | list-name } {none | local | group tacacs+ | group radius | group group-name }
| exec | Configures authorization for an interactive (EXEC) session. |
| nacm |
Enables the NACM (NETCONF Access Control Model) functionality. |
| default |
Uses the listed authorization methods that follow this keyword as the default list of methods for authorization. |
|
list-name |
Character string used to name the list of authorization methods. |
|
none |
Uses no authorization. If you specify none, no subsequent authorization method is attempted. |
|
local |
Uses local authorization. This method of authorization is not available for command authorization. |
|
group tacacs+ |
Uses the list of all configured TACACS+ servers for authorization. |
|
group radius |
Uses the list of all configured RADIUS servers for authorization. This method of authorization is not available for command authorization. |
|
group group-name |
Specifies a named subset of TACACS+ or RADIUS servers for authorization. |
Authorization is disabled for all actions (equivalent to the method none keyword).
Global configuration
| Release | Modification |
|---|---|
| R7.0.1 |
This command was introduced. |
The following example shows how to define the network authorization method list named listname1, which specifies that TACACS+ authorization is used.
configure
aaa authorization exec listname1 group tacacs+
exit
commit
To enable a Call Home profile, use the active command in the call home profile configuration mode.
active
|
This command has no keywords or arguments. |
None
Call home profile configuration mode
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command was introduced. |
You must enable a profile using the active command so that call home messages can be triggered.
The following example shows how to activate a profile.
domain name-server 64.102.6.247
call-home
service active
contact smart-licensing
profile CiscoTAC-1
active
To configure the IP address of the peer node during keyring configuration, use the address command in keyring configuration mode.
address { ipv4-address [ subnet-mask]}
| ipv4-address |
IP address of the peer node. |
| subnet-mask |
Subnet mask address. |
None
Keyring configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command was introduced. |
The following is a sample in which an OTNSec policy is configured.
RP/0/RP0/CPU0:ios#conf
Thu Mar 7 19:33:14.594 UTC
RP/0/RP0/CPU0:ios(config)#keyring kyr1
RP/0/RP0/CPU0:ios(config-keyring-kyr1)#peer peer1
RP/0/RP0/CPU0:ios(config-keyring-kyr1-peer-peer1)#address 10.0.0.1 255.255.255.0
RP/0/RP0/CPU0:ios(config-keyring-kyr1-peer-peer1)#pre-shared-key key1|clear
RP/0/RP0/CPU0:ios(config-keyring-kyr1-peer-peer1)#commit
Thu Mar 7 19:54:33.314 UTC
RP/0/RP0/CPU0:ios(config-keyring-kyr1-peer-peer1)#exit
RP/0/RP0/CPU0:ios(config-keyring-kyr1)#exit
RP/0/RP0/CPU0:ios(config)#exit
RP/0/RP0/CPU0:ios#show keyring kyr1
Thu Mar 7 19:58:07.135 UTC
Keyring Name : kyr1
===============================================================================
Total Peers : 1
-------------------------------------------------------------------------------
Peer Name : peer1
IP Address : 10.0.0.1
Subnet Mask : 255.255.255.0
Local PSK : Configured
Remote PSK : Configured
To configure the default AINS settings for all controllers on the OTN-XP card, use the ains-soak command in the IOS XR configuration mode. The configuration is applied to any OTN-XP line card that is installed in the Cisco NCS 1004.
ains-soak hours hours minutes minutes
| ains-soak hours hours minutes minutes |
Specifies the AINS configuration in hours and minutes. |
None
Cisco IOS XR Configuration
| Release | Modification |
|---|---|
| Release 7.2.1 |
This command was introduced. |
The following is a sample in which all the controllers on the OTN-XP card are configured with AINS with soak time period specified to be two minutes.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#ains-soak hours 0 minutes 2
RP/0/RP0/CPU0:ios(config)#commit
To override the default AINS settings on a specific controller on the OTN-XP card, use the automatic-in-service command.
![]() Note |
This configuration does not persist after a RP reload operation. |
automatic-in-service controller optics R/S/I/P hours hours minutes minutes
|
R/S/I/P |
Rack/Slot/Instance/Port of the optics controller. |
| hours minutes minutes |
Specifies the AINS configuration in hours and minutes. |
None
None
| Release | Modification |
|---|---|
| Release 7.2.1 |
This command was introduced. |
The following is a sample in which the optics controller on the OTN-XP card is configured with a soak time period of 45 minutes.
RP/0/RP0/CPU0:ios#automatic-in-service controller optics 0/1/0/0 hours 0 minutes 45
![]() Note |
You can specify only one local authentication method but multiple remote authentication methods. |
authentication {local pre-share | rsa-signature} {remote pre-share | rsa-signature}
| pre-share | Specifies the preshared key as the authentication method. |
| rsa-signature |
Specifies RSA signature as the authentication method. |
None
IKEv2 profile configuration
| Release | Modification |
|---|---|
| R7.2.1 |
This command was introduced. |
The following example shows how to specify the authentication mode in the IKEv2 profile.
RP/0/RP0/CPU0:ios#configure
Thu May 7 16:22:33.804 IST
RP/0/RP0/CPU0:ios(config)#ikev2 profile IP1
RP/0/RP0/CPU0:ios(config-ikev2-profile-IP1)#match identity remote address 1.1.1.2
255.255.255.255
RP/0/RP0/CPU0:ios(config-ikev2-profile-IP1)#pki trustpoint myca
RP/0/RP0/CPU0:ios(config-ikev2-profile-IP1)#lifetime 120
RP/0/RP0/CPU0:ios(config-ikev2-profile-IP1)#authentication local rsa-signature
RP/0/RP0/CPU0:ios(config-ikev2-profile-IP1)#authentication remote rsa-signature
RP/0/RP0/CPU0:ios(config-ikev2-profile-IP1)#commit
To specify the encryption algorithm for an OTNSec policy, use the cipher-suite command in the OTNSec policy configuration mode.
cipher-suite encryption-algorithm-type
| encryption-algorithm-type |
Encryption algorithm type. AES-GCM-256 is used. |
None
OTNSec policy configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command was introduced. |
The following is a sample in which an OTNSec policy is configured.
RP/0/RP0/CPU0:ios#configure
Mon Mar 11 15:16:58.417 UTC
RP/0/RP0/CPU0:ios(config)#otnsec policy otnsec-policy1
RP/0/RP0/CPU0:ios(config-otnsec-policy)#cipher-suite AES-GCM-256
RP/0/RP0/CPU0:ios(config-otnsec-policy)#security-policy must-secure
RP/0/RP0/CPU0:ios(config-otnsec-policy)#sak-rekey-interval 120
RP/0/RP0/CPU0:ios(config-otnsec-policy)#commit
The following is a sample of an OTNSec policy.
RP/0/RP0/CPU0:ios#show run otnsec policy otnsec-policy1
Tue Mar 12 11:14:03.591 UTC
otnsec policy otnsec-policy1
cipher-suite AES-GCM-256
security-policy must-secure
sak-rekey-interval 120
!
To configure the coherent DSP controller, use the controller coherentDSP command in the Coherent DSP controller configuration mode.
controller coherentDSP R/S/I/P [ description ] | [ fec fec-value ] | [ pm { 30-sec |15-min | 24-hour } { fec | otn } { report | threshold } value ] | [ perf-mon { enable | disable } ] | [ loopback internal ] | [ secondary-admin-state { maintenance | normal }] | [ shutdown ] | [ tti { sent | expected } { ascii | hex } tti-string ][ gcc0
| R/S/I/P |
Rack/Slot/Instance/Port of the coherent DSP controller. |
| description description |
Description of the coherent DSP controller. |
|
fec fec-value |
Configures the FEC on the controller. The supported options on the 1.2T line card are StandardSD15 and StandardSD27. Starting with R7.2.1, the supported options on the OTN XP line card are EnhancedSD15 and EnhancedSD27. |
|
pm { 30-sec |15-min | 24-hour} { fec | otn} { report | threshold} value |
Configures performance monitoring parameters for 30 second,15 minute, or 24 hour intervals. The fec keyword configures FEC PM data in 30 second, 15 minute, or 24 hour intervals. The otn keyword configures OTN PM data in 30 second, 15 minute, or 24 hour intervals. The report keyword configures TCA reporting status. The threshold keyword configures threshold values on PM parameters. |
|
perf-mon { enable | disable } |
Enables or disables performance monitoring. |
|
loopback internal |
Configures the internal loopback mode on the controller. For the 1.2T line card, internal and line loopbacks are supported on the Ethernet controllers whereas only internal loopback is supported on the CoherentDSP controllers. |
|
secondary-admin-state |
Configures the administrative state of the controller. The values are maintenance or normal. |
|
shutdown |
Disables the configuration of the controller. |
|
tti sent {ascii | hex} tti-string |
Configures the Trail Trace Identifier (TTI) ASCII or hex string to be sent. SAPI, DAPI, and operator inputs are not supported. |
|
tti expected {ascii | hex} tti-string |
Configures the expected TTI ASCII or hex string. The OTUK-TIM alarm is raised if the received TTI string does not match the expected TTI string. SAPI, DAPI, and operator inputs are not supported. |
|
gcc0 |
Enables the GCC0 interface. |
None
Coherent DSP controller configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command was introduced. |
| Release 7.1.1 |
gcc0 keyword was added. |
|
Release 7.2.1 |
The following FEC options for the OTN-XP card were added.
|
The following is a sample in which performance monitoring parameters of Coherent DSP controller is configured in 30 second intervals.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller coherentDSP 0/0/1/1 pm 30-sec fec threshold post-fec-ber max OE-15
RP/0/RP0/CPU0:ios(config)#commit
The following example shows how to configure TTI on a coherentDSP controller with the sent and expected strings set to the same ASCII string. The state of the controller is up.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller coherentDSP 0/1/0/1 tti sent ascii 1234
RP/0/RP0/CPU0:ios(config)#controller coherentDSP 0/1/0/1 tti expected ascii 1234
RP/0/RP0/CPU0:ios(config)#commit
The following example shows how to configure TTI on a coherentDSP controller with the sent and expected strings set to different ASCII strings. The state of the controller goes down and the OTUK-TIM alarm is raised.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller coherentDSP 0/1/0/1 tti sent ascii 1234
RP/0/RP0/CPU0:ios(config)#controller coherentDSP 0/1/0/1 tti expected ascii 5678
RP/0/RP0/CPU0:ios(config)#commit
The following is a sample to enable the GCC0 interface.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller CoherentDSP0/0/0/0
RP/0/RP0/CPU0:ios(config-CoDSP)#gcc0
RP/0/RP0/CPU0:ios(config-CoDSP)#commit
RP/0/RP0/CPU0:ios(config-CoDSP)#exit
The following is a sample to configure FEC with the EnhancedSD15 option on the CoherentDSP controller of the OTN-XP card:
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller coherentDSP 0/0/0/0
RP/0/RP0/CPU0:ios(config-CoDSP)#fec EnhancedSD15
Tue Feb 25 11:25:52.670 UTC
WARNING! Changing FEC mode can impact traffic
RP/0/RP0/CPU0:ios(config-CoDSP)#commit
To configure the Ethernet controller, use the controller HundredGigECtrlr command in the Ethernet controller configuration mode.
controller HundredGigECtrlr R/S/I/P [ pm { 30-sec |15-min | 24-hour} { ether} { report | threshold} value ] | [ perf-mon disable ] | [ loopback { internal | line} ] | [ sec-admin-state maintenance] | [ shutdown ] | [ laser-squelch] | [ fec { none | standard } ] | [ holdoff-time trunk-fault timevalue]
| R/S/I/P |
Rack/Slot/Instance/Port of the Ethernet controller. |
|
pm { 30-sec | 15-min | 24-hour } |
Configures performance monitoring parameters for 30 second, 15 minutes, or 24 hour intervals. |
|
ether |
Configures Ethernet PM data in 30 second, 15 minute or 24 hour intervals. |
|
report |
Configures TCA reporting status. |
|
threshold |
Configures threshold on Ethernet controller parameters. |
|
perf-mon disable |
Disables performance monitoring. |
|
loopback [ internal | line ] |
Configures the internal or line loopback mode on the Ethernet controller. For the 1.2T line card, internal and line loopbacks are supported on the ethernet controllers whereas only internal loopbacks are supported on the CoherentDSP controllers. |
|
sec-admin-state maintenance |
Configures the administrative state of the controller indicating that the controller is under maintenance. |
|
shutdown |
Disables the configuration of the controller. |
|
laser-squelch |
Enables laser squelching so that laser is brought down in the event of trunk faults (LOF, LOS) and a SQUELCHED alarm is raised. |
|
fec { none | standard } |
Disables FEC or enables standard (Reed-Solomon) FEC. |
|
holdoff-time trunk-fault timevalue |
When a fault occurs on the trunk port, the user can hold the propagation of Local Fault using this parameter. The range of timevalue is 0 to 3000 ms. |
None
Ethernet controller configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command was introduced. |
The following example shows how to configure the performance monitoring parameters of the Ethernet controller in 15 minute intervals.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller HundredGigECtrlr 0/1/0/10 pm 15-min pcs report bip enable
The following example shows how to configure the internal loopback.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller HundredGigECtrlr 0/1/0/10 secondary-admin-state maintenance
RP/0/RP0/CPU0:ios(config)#controller HundredGigECtrlr 0/1/0/10 loopback internal
RP/0/RP0/CPU0:ios(config)#commit
The following example enables IDLE hold off timer in Ethernet controller.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller HundredGigECtrlr 0/1/0/10 holdoff-time trunk-fault 3000
RP/0/RP0/CPU0:ios(config)#commit
The following is a sample where laser quelching is enabled on the Ethernet controller.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller HundredGigECtrlr 0/1/0/10 laser-squelch
RP/0/RP0/CPU0:ios(config)#commit
To configure the Ethernet controller, use the controller TenGigECtrlr command in the Ethernet controller configuration mode.
From R7.2.1 onwards, the TenGig Ethernet controller configuration is supported on the OTN-XP card.
controller TenGigECtrlr R/S/I/P/L [ pm { 30-sec |15-min | 24-hour } perf-mon disable ] | [ loopback { internal | line } ] | [ sec-admin-state maintenance ] | [ shutdown ] | [ laser-squelch ] | [ holdoff-time trunk-fault timevalue ]
| R/S/I/P/L |
Rack/Slot/Instance/Port/Lane of the Ethernet controller. |
|
pm { 30-sec | 15-min | 24-hour } |
Configures performance monitoring parameters for 30 second, 15 minutes, or 24 hour intervals. |
|
perf-mon disable |
Disables performance monitoring. |
|
loopback [ internal | line ] |
Configures the internal or line loopback mode on the Ethernet controller. |
|
sec-admin-state maintenance |
Configures the administrative state of the controller indicating that the controller is under maintenance. |
|
shutdown |
Disables the configuration of the controller. |
|
laser-squelch |
Enables laser squelching so that laser is brought down in the event of trunk faults and a SQUELCHED alarm is raised. |
|
holdoff-time trunk-fault timevalue |
When a fault occurs on the trunk port, the user can hold the propagation of Local Fault using this parameter. The range of timevalue is 0 to 3000 ms. |
None
Ethernet controller configuration
| Release | Modification |
|---|---|
| Release 7.2.1 |
This command was introduced. |
The following example shows how to configure the internal loopback.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller TenGigECtrlr 0/0/0/4/1secondary-admin-state maintenance
RP/0/RP0/CPU0:ios(config)#controller TenGigECtrlr 0/0/0/4/1 loopback internal
RP/0/RP0/CPU0:ios(config)#commit
The following example enables IDLE hold off timer in Ethernet controller.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller TenGigECtrlr 0/0/0/4/1 holdoff-time trunk-fault 3000
RP/0/RP0/CPU0:ios(config)#commit
The following is a sample where laser quelching is enabled on the Ethernet controller.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller TenGigECtrlr 0/0/0/4/1 laser-squelch
RP/0/RP0/CPU0:ios(config)#commit
To configure the ODU2e controller, use the controller odu2e command in the configuration mode.
From R7.2.1 onwards, the PBRS mode configuration is supported on the ODU2e controller on OTN-XP card.
controller Odu2e R/S/I/P/C/L opu prbs mode { source | sink | source-sink } pattern invertedpn31
| R/S/I/P/C/L |
Rack/Slot/Instance/Port/Client-port/Lane-number of the ODU2e controller. |
|
opu |
Configures Optical Channel Payload Unit (OPU) on the ODU2e controller. |
|
prbs mode { source| sink| source-sink} |
Configures Pseudo Random Binary Sequence (PRBS) mode as source, sink, or source sink. |
|
patterninvertedpn31 |
Configures PRBS pattern as inverted pattern. Sequence length is from 2^31 -1 bits. |
None
Configuration
| Release | Modification |
|---|---|
| Release 7.2.1 |
This command was introduced. |
The following is a sample in which PRBS mode is configured as source with pattern as invertedpn31.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller odu2e 0/0/0/0/4/1
RP/0/RP0/CPU0:ios(config-odu2e)#opu
RP/0/RP0/CPU0:ios(config-Opuk)#prbs mode source pattern invertedpn31
RP/0/RP0/CPU0:ios(config-Opuk)#commit
To configure the ODU4 controller, use the controller ODU4 command in the configuration mode.
controller ODU4 R/S/I/P gcc2
| R/S/I/P/L |
Rack/Slot/Instance/Port/Lane of the ODU4 controller. |
|
gcc2 |
Enables the GCC2 interface. |
None
Configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
|
Release 7.1.1 |
gcc2 keyword was added. |
The following is a sample in which OTNSec is configured on ODU4 controllers.
RP/0/RP0/CPU0:ios#configure
Mon Mar 12 12:10:21.374 UTC
RP/0/RP0/CPU0:ios(config)#controller ODU4 0/1/0/0/1
RP/0/RP0/CPU0:ios(config-odu4)#otnsec
RP/0/RP0/CPU0:ios(config-otnsec)#source ipv4 10.0.0.1
RP/0/RP0/CPU0:ios(config-otnsec)#destination ipv4 10.0.0.2
RP/0/RP0/CPU0:ios(config-otnsec)#session-id 9000
RP/0/RP0/CPU0:ios(config-otnsec)#policy otnsec-policy1
RP/0/RP0/CPU0:ios(config-otnsec)#ikev2 profile1
RP/0/RP0/CPU0:ios(config-otnsec)#commit
Mon Mar 12 12:14:17.609 UTC
RP/0/RP0/CPU0:ios(config-otnsec)#exit
RP/0/RP0/CPU0:ios(config)#exit
The following is a running configuration on an ODU4 controller.
RP/0/RP0/CPU0:ios#show run controller ODU4 0/1/0/0/1
Tue Mar 12 12:20:49.153 UTC
controller ODU40/1/0/0/1
gcc2
otnsec
policy otnsec-policy1
source ipv4 10.0.0.1
destination ipv4 10.0.0.2
session-id 9000
!
!
The following is a sample to enable the GCC2 interface.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller odu4 0/1/0/0/1
RP/0/RP0/CPU0:ios(config-odu4)#gcc2
RP/0/RP0/CPU0:ios(config-odu4)#commit
RP/0/RP0/CPU0:ios(config-odu4)#exit
To configure the OTU controller, use the controller OTU command in the configuration mode.
From R7.2.1 onwards, you can configure loopback on the OTU2, OTU2e, and OTU4 controllers on OTN-XP card.
controller { otu2 | otu2e | otu4 } R/S/I/P/L sec-admin-state loopback [ internal | line ]
| R/S/I/P/L |
Rack/Slot/Instance/Port/Lanenumber of the OTU2, OTU2e, and OTU4 controller. The range of Lanenumber is from 1 to 4. |
|
sec-admin-state |
Configures the administrative state of the controller . |
|
loopback [ internal | line ] |
Configures the internal or line loopback mode on the OTU2, OTU2e, and OTU4 controller. |
None
Configuration
| Release | Modification |
|---|---|
| Release 7.2.1 |
This command was introduced. |
The following is a sample in which the line loopback is configured on the OTU2e controller.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller otu2e 0/0/0/11/3
RP/0/RP0/CPU0:ios(config-otu2e)#secondary-admin-state maintenance
RP/0/RP0/CPU0:ios(config-otu2e)#loopback line
RP/0/RP0/CPU0:ios(config-otu2e)#commit
Thu Apr 23 10:55:19.319 UTC
RP/0/RP0/CPU0:ios(config-otu2e)#end
The following is a sample in which the internal loopback is configured on the OTU2 controller.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller otu2 0/0/0/5/1
RP/0/RP0/CPU0:ios(config-otu2)#secondary-admin-state maintenance
RP/0/RP0/CPU0:ios(config-otu2)#loopback internal
RP/0/RP0/CPU0:ios(config-otu2)#commit
Thu Apr 23 11:01:00.562 UTC
RP/0/RP0/CPU0:ios(config-otu2)#end
The following is a sample in which the internal loopback is configured on the OTU4 controller.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller otu4 0/0/0/0
RP/0/RP0/CPU0:ios(config-otu4)#secondary-admin-state maintenance
RP/0/RP0/CPU0:ios(config-otu4)#loopback internal
RP/0/RP0/CPU0:ios(config-otu4)#commit
Thu Apr 23 11:05:22.429 UTC
RP/0/RP0/CPU0:ios(config-otu4)#end
To configure the optics controller, use the controller optics command in the optics controller configuration mode.
controller optics R/S/I/P [ baud-rate rate] [ bits-per-symbol value] [ cd-max cd-max | cd-min cd-min | cd-low-threshold cd-low | cd-high-threshold cd-high | dgd-high-threshold dgd-value | lbc-high-threshold lbc-value | osnr-low-threshold osnr-value description description | rx-high-threshold rx-high | rx-low-threshold rx-low | tx-high-threshold tx-high | tx-low-threshold tx-low | sec-admin-state {maintenance | normal} | shutdown | transmit-power transmit-power | transmit-shutdown | perf-mon { enable | disable } | pm [ 30-sec |15-min | 24-hour ] optics [ report | threshold { cd | dgd | lbc | lbc-pc | opr | opt | osnr | pcr | pdl | pn | sopmd | rx-sig-pow | rx-sig-pow-dbm }]
To configure the sub-sea parameters for the optics controller, use the following command:
controller optics R/S/I/P [ filter-roll-off-factor value | filter-roll-off-factor value | rx-voa target-power value | rx-voa fixed-ratio value | enh-colorless-mode value | enh-sop-tol-mode value | nleq-comp-mode value | cross-pol-gain-mode value | cross-pol-weight-mode value | cpr-win-mode value | cpr-ext-win-mode value | submarine-params type value ]
For more information about the sub-sea parameters, see the Configuration Guide for Cisco NCS 1004, IOS XR Release 7.0.1.
| R/S/I/P |
Rack/Slot/Instance/Port of the optics controller. |
||
|
baud-rate rate |
Sets baud-rate for this controller in GBd. |
||
|
bits-per-symbol value |
Sets bits-per-symbol for this controller. |
||
| cd-max cd-max |
(Only for trunk optics controllers) Maximum chromatic dispersion. The range is -350000 to +350000 ps/nm. |
||
| cd-min cd-min |
(Only for trunk optics controllers) Minimum chromatic dispersion. The range is -350000 to +350000 ps/nm. |
||
| cd-low-threshold cd-low |
(Only for trunk optics controllers) Minimum acceptable chromatic dispersion. The CD alarm is raised if the chromatic dispersion goes below this value. The range is -350000 to +350000 ps/nm. |
||
| cd-high-threshold cd-high |
(Only for trunk optics controllers) Maximum acceptable chromatic dispersion. The CD alarm is raised if the chromatic dispersion exceeds this value. The range is -350000 to +350000 ps/nm. |
||
| dgd-high-threshold dgd-value |
(Only for trunk optics controllers) Configures the maximum acceptable Differential Group Delay (DGD) value. The DGD alarm is raised if DGD exceeds this value. The range is 0 to 18000 (in the units of 0.01 ps). |
||
| lbc-high-threshold lbc-value |
Configures the high laser bias current threshold. The range is 0 to 100% |
||
| osnr-low-threshold osnr-value |
(Only for trunk optics controllers) Configures the minimum acceptable Optical Signal to Noise ratio (OSNR) value. The OSNR alarm is raised if OSNR goes below this value. The range is 0 to 4000 (in units of 0.01db). |
||
| description description |
Description of the optics controller. |
||
|
rx-high-threshold rx-high |
Configures high receive power threshold. The range is -400 to 300 (in the units of 0.1 dBm). |
||
|
rx-low-threshold rx-low |
Configures low receive power threshold. The range is -400 to 300 (in the units of 0.1 dBm). |
||
|
tx-high-threshold tx-high |
Configures high transmit power threshold. The range is -400 to 300 dBm (in the units of 0.1 dBm). |
||
|
tx-low-threshold tx-low |
Configures low transmit power threshold. The range is -400 to 300 dBm (in the units of 0.1 dBm). |
||
|
sec-admin-state |
Configures the administrative state of the controller. The values are maintenance or normal. |
||
|
shutdown |
Disables the configuration of the controller. |
||
|
pm |
Configures performance monitoring parameters for 30 second, 15 minute, and 24 hour intervals. |
||
|
transmit-power transmit-power |
(Only for trunk optics controllers) Configures the transmit power. The range is -190 to 30 dBm (in the units of 0.1 dBm). |
||
|
transmit-shutdown |
Shuts down the transmit laser. |
||
|
perf-mon { enable | disable } |
Enables or disables performance monitoring. |
||
|
cd |
Configures the chromatic dispersion threshold. |
||
|
dgd |
Configures the differential group delay threshold. |
||
|
lbc |
Configures the laser bias current threshold. |
||
|
lbc-pc |
Configures the laser bias current threshold in percentage. |
||
|
opr |
Configures the optical Rx power threshold in uW. |
||
|
opt |
Configures the optical Tx power threshold in uW. |
||
|
osnr |
Configures the OSNR threshold. |
||
|
pcr |
Configures the Polarization Change Rate (PCR) threshold. |
||
|
pdl |
Configures the Polarization Dependent Loss (PDL) threshold. |
||
|
pn |
Configures the Phase Noise (PN) threshold. |
||
|
sopmd |
Configures the Second Order Polarization Mode Dispersion (SOPMD) threshold. |
||
|
rx-sig-pow |
Configures the Rx signal power threshold in uW. |
||
|
rx-sig-pow-dbm |
Configures the Rx signal power threshold in dBm. The unit is 0.01 dBm. |
||
|
filter-roll-off-factor value |
Configures the RRC filter roll-off factor. The range is 0 to 1. |
||
|
rx-voa target-power value |
Configures the receive target power. The range is -190 to +30. |
||
|
rx-voa fixed-ratio value |
Configures the receive ratio of optical attenuation. The range is +100 to +1700. |
||
|
enh-colorless-mode value |
Configures the enhanced colorless mode. The range is 1 to 3. |
||
|
enh-sop-tol-mode value |
Configures the enhanced SOP tolerance mode. The range is 1 to 3. |
||
|
nleq-comp-mode value |
Configures the non-linear compensation. The range is 1 to 4. |
||
|
cross-pol-gain-mode value |
Configures the carrier phase recovery cross polarization gain mode. The range is 0 to 15. |
||
|
cross-pol-weight-mode value |
Configures the carrier phase recovery cross polarization weight mode. The range is 0 to 15. |
||
|
cpr-win-mode value |
Configures the carrier phase recovery window mode. The range is 1 to 4. |
||
|
cpr-ext-win-mode value |
Configures the carrier phase recovery extended window mode. The range is 1 to 15. |
||
|
submarine-params type value |
Configures the proprietary submarine parameters. The range for the type is 1 to 10 and the range for the value is 1 to 1000.
|
None
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command was introduced. |
Optics controller configuration
The configurations for chromatic dispersion (cd-max, cd-min, cd-low-threshold, and cd-high-threshold) must be performed only after the hw-module configuration. These configurations must be removed before the no hw-module configuration.
The following example shows how to configure the optics controller and set the high power threshold at the transmit and receive side.
RP/0/RP0/CPU0:ios# configure
RP/0/RP0/CPU0:ios(config)#controller optics 0/0/1/1
RP/0/RP0/CPU0:ios(config-optics)#rx-high-threshold 200
RP/0/RP0/CPU0:ios(config-optics)#tx-high-threshold 300
The following example shows how to configure the optics controller and set the ranges for chromatic dispersion.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller optics 0/0/1/1
RP/0/RP0/CPU0:ios(config-optics)#cd-max 10000
RP/0/RP0/CPU0:ios(config-optics)#cd-min 2000
The following is a sample in which the performance monitoring parameters of optics controller is configured in 24 hour intervals.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller optics 0/0/1/1 pm 24-hour optics threshold osnr max 345
RP/0/RP0/CPU0:ios(config)#commit
To specify the destination address for Smart Call Home, use the destination address command in the call home profile configuration mode.
destination address address
|
address |
Specifies the destination address for Smart Call Home. The format is {http|https}://{FQDN}/its/service/oddce/services/DDCEService FQDN must be either Cisco Smart Software Manager FQDN (tools.cisco.com) or Smart Licensing satellite server FQDN. |
None
Call home profile configuration mode
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command was introduced. |
You must configure the DNS server before setting-up the call-home destination address as FQDN. Use domain name-server {DNS server IP} command to configure the DNS server on the device.
The following example shows how to specify the destination address for Smart Call Home.
domain name-server 64.102.6.247
call-home
service active
contact smart-licensing
profile CiscoTAC-1
active
destination address http https://tools.cisco.com/its/service/oddce/services/DDCEService
To specify the destination of a GMPLS UNI tunnel, use the destination ipv4 unicast command in GMPLS UNI controller tunnel-properties configuration sub-mode.
destination ipv4 unicast address
| address |
Specifies the tunnel destination (IPv4 address). |
None
GMPLS UNI controller tunnel-properties configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
The following example shows how to specify a tunnel destination (10.10.3.4).
RP/0/RP0/CPU0:ios(config)#mpls traffic-eng
RP/0/RP0/CPU0:ios(config-mpls-te)#gmpls optical-uni
RP/0/RP0/CPU0:ios(config-te-gmpls)#controller Optics0/0/0/0
RP/0/RP0/CPU0:ios(config-te-gmpls-cntl)#tunnel-properties
RP/0/RP0/CPU0:ios(config-te-gmpls-tun)#destination 10.10.3.4
RP/0/RP0/CPU0:ios(config-te-gmpls-tun)#
To specify the destination transport method for Smart Call Home, use the destination transport-method command.
destination transport-method {http|email}
|
|
Enables an e-mail address for the profile. |
|
http |
Enables an HTTP URL for the profile. |
None
Call home profile configuration mode
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command was introduced. |
For the user profile, both e-mail and http can be enabled. For the Cisco TAC profile, only one transport method can be enabled.
The following example shows how to specify the destination transport method for Smart Call Home.
domain name-server 64.102.6.247
call-home
service active
contact smart-licensing
profile CiscoTAC-1
active
destination address http https://tools.cisco.com/its/service/oddce/services/DDCEService
destination transport-method http
To specify the Diffie-Hellman group for the IKEv2 proposal, use the dh command in IKEv2 proposal configuration mode.
dh dh-group
| dh-group |
DH group identifier. The possible values are 19, 20, and 21. |
None
IKEv2 proposal configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
The following is a sample in which an IKEv2 proposal is configured.
RP/0/RP0/CPU0:ios#configure
Thu Mar 7 19:19:30.259 UTC
RP/0/RP0/CPU0:ios(config)#ikev2 proposal proposal1
RP/0/RP0/CPU0:ios(config-ikev2-proposal-proposal1)#encryption aes-cbc-256
RP/0/RP0/CPU0:ios(config-ikev2-proposal-proposal1)#integrity sha-1
RP/0/RP0/CPU0:ios(config-ikev2-proposal-proposal1)#prf sha-256
RP/0/RP0/CPU0:ios(config-ikev2-proposal-proposal1)#dh 20
RP/0/RP0/CPU0:ios(config-ikev2-proposal-proposal1)#commit
Thu Mar 7 19:20:30.916 UTC
RP/0/RP0/CPU0:ios(config-ikev2-proposal-proposal1)#exit
RP/0/RP0/CPU0:ios(config)#exit
RP/0/RP0/CPU0:ios#show ikev2 proposal proposal1
Thu Mar 7 19:20:48.929 UTC
Proposal Name : proposal1
=====================================================================================
Status : Complete
-------------------------------------------------------------------------------------
Total Number of Enc. Alg. : 1
Encr. Alg. : CBC-AES-256
-------------------------------------------------------------------------------------
Total Number of Hash. Alg. : 1
Hash. Alg. : SHA 1
-------------------------------------------------------------------------------------
Total Number of PRF. Alg. : 1
PRF. Alg. : SHA 256
-------------------------------------------------------------------------------------
Total Number of DH Group : 1
DH Group : Group 20
To configure the wavelength on the trunk port, use the dwdm-carrier command in optics controller configuration mode. To return the wavelength to its default value, use the no form of this command.
dwdm-carrier { 100MHz-grid frequency frequency } | { 50GHz-grid frequency frequency }
| 50Ghz-grid | 100MHz-grid |
Configures the wavelength in 50GHz grid and 100MHz (0.1GHz) grid spacing respectively in accordance with ITU definition. |
| frequency frequency |
Specifies the frequency for the optics controller. |
None
Optics controller configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command was introduced. |
The controller must be in the shutdown state before you can use the wavelength command.
The following example shows how to configure the frequency in 100MHz grid spacing.
RP/0/RP0/CPU0:ios# config
RP/0/RP0/CPU0:ios(config)# controller optics 0/0/0/0
RP0/0/CPU0:ios(config-optics)# dwdm-carrier 100MHz-grid frequency 1865000
To specify the transform types for encryption, use the encryption command in the IKEv2 proposal configuration mode.
encryption encryption-type
| encryption-type |
Encrytion algorithm. The possible values are aes-gcm-256, aes-gcm-128, aes-cbc-256, aes-cbc-192, and aes-cbc-128. |
None
IKEv2 proposal configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
The following is a sample in which an IKEv2 proposal is configured.
RP/0/RP0/CPU0:ios#configure
Thu Mar 7 19:19:30.259 UTC
RP/0/RP0/CPU0:ios(config)#ikev2 proposal proposal1
RP/0/RP0/CPU0:ios(config-ikev2-proposal-proposal1)#encryption aes-cbc-256
RP/0/RP0/CPU0:ios(config-ikev2-proposal-proposal1)#integrity sha-1
RP/0/RP0/CPU0:ios(config-ikev2-proposal-proposal1)#prf sha-256
RP/0/RP0/CPU0:ios(config-ikev2-proposal-proposal1)#dh 20
RP/0/RP0/CPU0:ios(config-ikev2-proposal-proposal1)#commit
Thu Mar 7 19:20:30.916 UTC
RP/0/RP0/CPU0:ios(config-ikev2-proposal-proposal1)#exit
RP/0/RP0/CPU0:ios(config)#exit
RP/0/RP0/CPU0:ios#show ikev2 proposal proposal1
Thu Mar 7 19:20:48.929 UTC
Proposal Name : proposal1
=====================================================================================
Status : Complete
-------------------------------------------------------------------------------------
Total Number of Enc. Alg. : 1
Encr. Alg. : CBC-AES-256
-------------------------------------------------------------------------------------
Total Number of Hash. Alg. : 1
Hash. Alg. : SHA 1
-------------------------------------------------------------------------------------
Total Number of PRF. Alg. : 1
PRF. Alg. : SHA 256
-------------------------------------------------------------------------------------
Total Number of DH Group : 1
DH Group : Group 20
Use the fault-profile command in the global configuration mode, to create a new fault profile with one or more alarms and user-defined severity.
fault-profile name fault-identifier subsystem XR fault-type { ethernet | sdh_controller | sonet | OPTICS | G709 } fault-tag name sas severity nsas severity
| fault-profile name |
Name of the fault profile. |
| fault-identifier subsystem XR |
Supports the XR sub-system. |
| fault-type |
The component the fault profile is applicable to. The available options are:
|
| fault-tag name | The faults that are included as part of the newly created fault profile. |
| sas severity nsas severity |
Sets the severity level for:
The available options are:
|
No default behavior or values.
Global Configuration
| Release | Modification |
|---|---|
|
Release 7.1.1 |
This command was introduced. |
The following example shows how to use the fault profile command.
RP/0/RP0/CPU0: router (config) # fault profile f1 fault-identifier subsystem XR fault-type HW_OPTICS fault-tag OPTICAL_LO_RXPOWER sas CRITICAL nsas CRITICAL
Use the fault-profile apply command in the global configuration mode, to apply a fault profile at the node level or card level.
fault-profile name apply rack0 slot location
| fault-profile name |
Name of the fault profile. |
| rack 0 slot location |
Sets the profile at the node level or line card level. |
No default behavior or values.
Global Configuration
| Release | Modification |
|---|---|
|
Release 7.1.1 |
This command was introduced. |
The following example shows how to use the fault profile apply command.
RP/0/RP0/CPU0:ios(config)# fault profile f1 apply rack 0 slot ALL
To enable GMPLS UNI feature, use the gmpls optical-uni command in LMP configuration mode.
gmpls optical-uni
| This command has no keywords or arguments. |
None
LMP configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
The LMP submode enables GMPLS-UNI LMP functionality and acts as a container for other GMPLS-UNI LMP configuration commands.
The following example shows how to enable GMPLS UNI and enter LMP configuration mode.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#lmp
RP/0/RP0/CPU0:ios(config-lmp)#gmpls optical-uni
RP/0/RP0/CPU0:ios(config-lmp-gmpls)#
To configure the Call Home HTTP proxy server, use the http-proxy command in the call home profile configuration mode.
http-proxy proxy-server-name port port-number
|
proxy-server-name |
Specifies the name of the proxy server. |
|
port-number |
Specifies the port for the specified HTTP proxy server. |
None
Call home profile configuration mode
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command was introduced. |
None
The following example configures the call home HTTP proxy server :
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#call-home
RP/0/RP0/CPU0:ios(config-call-home)#http-proxy aa.bbb.cc.dd port 100
To configure the card in the module (muxponder), slice configuration (muxponder slice), or regen mode, use the hw-module command in IOS XR configuration mode.
hw-module location location { mxponder | mxponder-slice mxponder-slice-number } client bitrate [100GE | OTU4] trunk bitrate [150G | 200G | 250G | 300G | 350G | 400G | 450G | 500G | 550G | 600G] [drop-lldp] [client-port-ains-soak hours hours minutes minutes ]
hw-module location location { regen trunk-rate trunk-rate }
hw-module location location mxponder arp-snoop
| location location |
Specifies the location of the optics controller. |
||
| mxponder |
Configures the card in muxponder mode. |
||
| mxponder-slice mxponder-slice-number |
Configures the card in muxponder slice configuration. Slice numbers can be 0 or 1. |
||
| client bitrate [100GE | OTU4] |
Specifies the traffic rate on the client ports. The supported client rates are 100GE and OTU4. |
||
| trunk bitrate [150G | 200G | 250G | 300G | 350G | 400G | 450G | 500G | 550G | 600G] |
Specifies the traffic rate on the trunk ports. The supported trunk rates are 150G, 200G, 250G, 300G, 350G, 400G, 450G, 500G, 550G, and 600G.
|
||
|
drop-lldp |
Enables LLDP drop on a muxponder or muxponder slice. |
||
| client-port-ains-soak hours hours minutes minutes |
Specifies the AINS configuration in hours and minutes. |
||
| regen trunk-rate trunk-rate |
Configures the card in Regen mode. The supported trunk rates are 100G to 600G in multiples of 100G. |
||
| arp-snoop |
Configures MAC address or ARP snoop on the client ports. |
No slice is configured.
You must configure the card mode before enabling LLDP drop.
Cisco IOS XR Configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command was introduced. |
|
Release 7.1.1 |
regen keyword was added. |
|
Release 7.2.1 |
arp-snoop keyword was added. |
The following is a sample in which the card is configured in the muxponder mode with 100GE client payload and 500G trunk payload.
RP/0/RP0/CPU0:ios#configure
Sun Feb 24 14:09:33.989 UTC
RP/0/RP0/CPU0:ios(config)#hw-module location 0/2 mxponder client-rate 100GE
RP/0/RP0/CPU0:ios(config)#hw-module location 0/2 mxponder trunk-rate 500G
RP/0/RP0/CPU0:ios(config)#commit
The following is a sample in which the card is configured in the muxponder mode with a 550G trunk payload.
RP/0/RP0/CPU0:ios#config
Tue Oct 15 01:24:56.355 UTC
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder client-rate 100GE
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder trunk-rate 550G
RP/0/RP0/CPU0:ios(config)#commit
RP/0/RP0/CPU0:ios#configure
Sun Feb 24 14:09:33.989 UTC
RP/0/RP0/CPU0:ios(config)#hw-module location 0/2 mxponder client-rate OTU4
RP/0/RP0/CPU0:ios(config)#hw-module location 0/2 mxponder trunk-rate 500G
RP/0/RP0/CPU0:ios(config)#commitThe following is a sample in which the card is configured in the muxponder slice 0 mode with a 300G trunk payload.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder-slice 0 client-rate 100GE
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder-slice 0 trunk-rate 300G
RP/0/RP0/CPU0:ios(config)#commit
The following is a sample in which the card is configured in the muxponder slice 1 mode with a 400G trunk payload.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder-slice 1 client-rate 100GE
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder-slice 1 trunk-rate 400G
RP/0/RP0/CPU0:ios(config)#commit
The following example shows how to configure LLDP drop on a muxponder slice.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder-slice 0 drop-lldp
The following is a sample in which all the client ports are configured with AINS with soak time as 15 minutes.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#hw-module location 0/3 mxponder client-rate 100GE trunk-rate 500G
RP/0/RP0/CPU0:ios(config)#hw-module location 0/3 mxponder client-port-ains-soak hours 0 minutes 15
RP/0/RP0/CPU0:ios(config)#commit
The following is a sample to configure the card in Regen mode.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#hw-module location 0/0
RP/0/RP0/CPU0:ios(config-hwmod)#regen
RP/0/RP0/CPU0:ios(config-regen)#trunk-rate 400
RP/0/RP0/CPU0:ios(config-regen)#commit
RP/0/RP0/CPU0:ios(config-regen)#exit
The following is a sample in which the card is configured with mixed client rates in the muxponder slice mode.
RP/0/RP0/CPU0:ios#configure
Mon Mar 23 06:10:22.227 UTC
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder-slice 0 client-rate OTU4 trunk-rate 500G
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder-slice 1 client-rate 100GE trunk-rate 500G
RP/0/RP0/CPU0:ios(config)#commit
The following is a sample to configure MAC address or ARP snoop on client ports for Mxponder mode configuration.
RP/0/RP0/CPU0:ios#configure
Mon Mar 16 19:08:17.154 UTC
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder arp-snoop
RP/0/RP0/CPU0:ios(config)#commit
The following is a sample to configure MAC address snoop on client ports for slice mode configuration.
RP/0/RP0/CPU0:ios#configure
Mon Mar 16 19:30:33.933 UTC
RP/0/RP0/CPU0:ios(config)#hw-module location 0/3 mxponder-slice 0
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-rate 100GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#trunk-rate 600G
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#arp-snoop
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#commit
Mon Mar 16 19:30:52.636 UTC
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#end
To configure the OTN-XP card in the muxponder mode, use the hw-module command in IOS XR configuration mode.
hw-module location location mxponder-slice mxponder-slice-number trunk-rate 100G client-port-rate client-port-number lane lane number client-type [10GE | OTU2 | OTU2e]
| location location |
Specifies the location of the optics controller. |
| mxponder-slice mxponder-slice-number |
Configures the card in muxponder mode.The muxponder configuration supports two slices, 0 and 1. |
|
trunk-rate 100G |
Specifies the traffic rate on the trunk ports. The supported trunk rates is 100G. |
| client-port-rate client-port-number |
Specifies client port number.
|
|
lane lane-number |
Specifies client port lane number. |
|
client-type [10GE | OTU2 | OTU2e] |
Specifies the traffic type on the client ports. The supported client types are 10GE, OTU2, and OTU2e. |
None
Cisco IOS XR Configuration
| Release | Modification |
|---|---|
| Release 7.2.1 |
This command was introduced. |
The following is a sample in which the OTN-XP card is configured with mixed client rates in the mxponder-slice 0 mode.
RP/0/RP0/CPU0:ios#config
Tue Apr 21 09:21:44.460 UTC
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder-slice 0
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#trunk-rate 100G
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 2 lane 3 client-type OTU2
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 2 lane 4 client-type OTU2
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#commit
To specify an IKEv2 policy name, use the ikev2 policy command in configuration mode.
ikev2 policy policy-name
| policy-name |
IKEv2 policy name upto 32 characters. |
None
Configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
The following is a sample in which an IKEv2 policy is configured.
RP/0/RP0/CPU0:ios#configure
Thu Mar 7 19:26:45.752 UTC
RP/0/RP0/CPU0:ios(config)#ikev2 policy mypolicy
RP/0/RP0/CPU0:ios(config-ikev2-policy-mypolicy)#proposal proposal1
RP/0/RP0/CPU0:ios(config-ikev2-policy-mypolicy)#match address local 10.0.0.1
RP/0/RP0/CPU0:ios(config-ikev2-policy-mypolicy)#commit
Thu Mar 7 19:29:25.043 UTC
RP/0/RP0/CPU0:ios(config-ikev2-policy-mypolicy)#exit
RP/0/RP0/CPU0:ios(config)#exit
RP/0/RP0/CPU0:ios#show ikev2 policy mypolicy
Thu Mar 7 19:30:30.343 UTC
Policy Name : mypolicy
===============================================================================
Total number of match local addr : 1
Match address local : 10.0.0.1
-------------------------------------------------------------------------------
Total number of proposal attached : 1
Proposal Name : proposal1
To configure an IKEv2 profile, use the ikev2 profile command in configuration mode.
ikev2 profile profile-name
| profile-name |
Name of the IKEv2 profile. |
None
Configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
The following is a sample in which an IKEv2 profile is configured.
RP/0/RP0/CPU0:ios#configure
Thu Mar 7 20:00:36.490 UTC
RP/0/RP0/CPU0:ios(config)#ikev2 profile profile1
RP/0/RP0/CPU0:ios(config-ikev2-profile-profile1)#match identity remote address 10.0.0.1 255.255.255.0
RP/0/RP0/CPU0:ios(config-ikev2-profile-profile1)#keyring kyr1
RP/0/RP0/CPU0:ios(config-ikev2-profile-profile1)#lifetime 120
RP/0/RP0/CPU0:ios(config-ikev2-profile-profile1)#commit
Thu Mar 7 20:15:03.401 UTC
RP/0/RP0/CPU0:ios(config-ikev2-profile-profile1)#exit
RP/0/RP0/CPU0:ios(config)#exit
RP/0/RP0/CPU0:ios#show ikev2 profile profile1
Thu Mar 7 20:15:25.776 UTC
Profile Name : profile1
===============================================================================
Keyring : kyr1
Lifetime(Sec) : 120
DPD Interval(Sec) : 10
DPD Retry Interval(Sec) : 2
Match ANY : NO
Total Match remote peers : 1
Addr/Prefix : 10.0.0.1/255.255.255.0
To specify an IKEv2 proposal name, use the ikev2 proposal command in the configuration mode .
ikev2 proposal proposal-name
| proposal-name |
Name of IKEv2 proposal upto 32 characters. |
None
Configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
The following is a sample in which an IKEv2 proposal is configured.
RP/0/RP0/CPU0:ios#configure
Thu Mar 7 19:19:30.259 UTC
RP/0/RP0/CPU0:ios(config)#ikev2 proposal proposal1
RP/0/RP0/CPU0:ios(config-ikev2-proposal-proposal1)#encryption aes-cbc-256
RP/0/RP0/CPU0:ios(config-ikev2-proposal-proposal1)#integrity sha-1
RP/0/RP0/CPU0:ios(config-ikev2-proposal-proposal1)#prf sha-256
RP/0/RP0/CPU0:ios(config-ikev2-proposal-proposal1)#dh 20
RP/0/RP0/CPU0:ios(config-ikev2-proposal-proposal1)#commit
Thu Mar 7 19:20:30.916 UTC
RP/0/RP0/CPU0:ios(config-ikev2-proposal-proposal1)#exit
RP/0/RP0/CPU0:ios(config)#exit
RP/0/RP0/CPU0:ios#show ikev2 proposal proposal1
Thu Mar 7 19:20:48.929 UTC
Proposal Name : proposal1
=====================================================================================
Status : Complete
-------------------------------------------------------------------------------------
Total Number of Enc. Alg. : 1
Encr. Alg. : CBC-AES-256
-------------------------------------------------------------------------------------
Total Number of Hash. Alg. : 1
Hash. Alg. : SHA 1
-------------------------------------------------------------------------------------
Total Number of PRF. Alg. : 1
PRF. Alg. : SHA 256
-------------------------------------------------------------------------------------
Total Number of DH Group : 1
DH Group : Group 20
To specify one or more transforms of the integrity algorithm type, use the integrity command in IKEv2 proposal configuration mode.
integrity algorithm-type
| algorithm-type |
Integrity algorithm type. The possible values are: sha-1, sha-256, sha-384, and sha-512. |
None
IKEv2 proposal configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
The following is a sample in which an IKEv2 proposal is configured.
RP/0/RP0/CPU0:ios#configure
Thu Mar 7 19:19:30.259 UTC
RP/0/RP0/CPU0:ios(config)#ikev2 proposal proposal1
RP/0/RP0/CPU0:ios(config-ikev2-proposal-proposal1)#encryption aes-cbc-256
RP/0/RP0/CPU0:ios(config-ikev2-proposal-proposal1)#integrity sha-1
RP/0/RP0/CPU0:ios(config-ikev2-proposal-proposal1)#prf sha-256
RP/0/RP0/CPU0:ios(config-ikev2-proposal-proposal1)#dh 20
RP/0/RP0/CPU0:ios(config-ikev2-proposal-proposal1)#commit
Thu Mar 7 19:20:30.916 UTC
RP/0/RP0/CPU0:ios(config-ikev2-proposal-proposal1)#exit
RP/0/RP0/CPU0:ios(config)#exit
RP/0/RP0/CPU0:ios#show ikev2 proposal proposal1
Thu Mar 7 19:20:48.929 UTC
Proposal Name : proposal1
=====================================================================================
Status : Complete
-------------------------------------------------------------------------------------
Total Number of Enc. Alg. : 1
Encr. Alg. : CBC-AES-256
-------------------------------------------------------------------------------------
Total Number of Hash. Alg. : 1
Hash. Alg. : SHA 1
-------------------------------------------------------------------------------------
Total Number of PRF. Alg. : 1
PRF. Alg. : SHA 256
-------------------------------------------------------------------------------------
Total Number of DH Group : 1
DH Group : Group 20
To configure the GCC0 interface, use the interface gcc0 command in configuration mode.
interface gcc0 R/S/I/P
| R/S/I/P |
Rack/Slot/Instance/Port of the GCC0 interface. |
None
Configuration
| Release | Modification |
|---|---|
| Release 7.1.1 |
This command is introduced. |
The following is a sample to configure the GCC0 interface using the static IP address.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#interface gcc0 0/1/0/0
P/0/RP0/CPU0:ios(config-if)#ipv4 address 10.1.1.1 255.255.255.0
RP/0/RP0/CPU0:ios(config-if)#commit
RP/0/RP0/CPU0:ios(config-if)#exit
RP/0/RP0/CPU0:ios(config)#exit
RP/0/RP0/CPU0:ios#show run interface gcc0 0/1/0/0
interface GCC00/1/0/0
ipv4 address 10.1.1.1 255.255.255.0
!
The following is a sample to configure the GCC0 interface using the loopback IP address.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:R2(config)#interface gcc0 0/1/0/0
RP/0/RP0/CPU0:R2(config-if)#ipv4 unnumbered loopback 0
RP/0/RP0/CPU0:ios(config-if)#exit
RP/0/RP0/CPU0:ios(config)#exit
To configure the GCC2 interface, use the interface gcc2 command in configuration mode.
interface gcc2 R/S/I/P/L
| R/S/I/P/L |
Rack/Slot/Instance/Port/Lane of the GCC2 interface. |
None
Configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
The following is a sample to configure the GCC2 interface using the static IP address.
RP/0/RP0/CPU0:ios#config
Tue Mar 12 11:16:04.749 UTC
RP/0/RP0/CPU0:ios(config)#interface gcc2 0/1/0/0/1
P/0/RP0/CPU0:ios(config-if)#ipv4 address 10.0.0.1 255.255.255.0
RP/0/RP0/CPU0:ios(config-if)#commit
Tue Mar 12 11:18:32.867 UTC
RP/0/RP0/CPU0:ios(config-if)#exit
RP/0/RP0/CPU0:ios(config)#exit
RP/0/RP0/CPU0:ios#show run interface gcc2 0/1/0/0/1
Tue Mar 12 11:19:00.475 UTC
interface gcc2 0/1/0/0/1
ipv4 address 10.0.0.1 255.255.255.0
!
The following is a sample to configure the GCC2 interface using the loopback IP address.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:R2(config)#interface gcc2 0/1/0/0/1
RP/0/RP0/CPU0:R2(config-if)#ipv4 unnumbered loopback 0
RP/0/RP0/CPU0:ios(config-if)#exit
RP/0/RP0/CPU0:ios(config)#exit
To specify the LMP neighbor IPCC configuration for GMPLS UNI, use the ipcc routed command in the neighbor sub-mode for LMP GMPLS-UNI controller configuration mode.
ipcc routed
| This command has no keywords or arguments. |
None
LMP GMPLS-UNI controller neighbor configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
The LMP submode enables GMPLS-UNI LMP functionality and acts as a container for other GMPLS-UNI LMP configuration commands.
The following example shows how to specify the IPCC configuration for the GMPLS UNI controller 0/0/0/0, neighbor UN02.
RP/0/RP0/CPU0:ios(config)#lmp
RP/0/RP0/CPU0:ios(config-lmp)#gmpls optical-uni
RP/0/RP0/CPU0:ios(config-lmp-gmpls-uni)#neighbor UN02
RP/0/RP0/CPU0:ios(config-lmp-gmpls-uni-nbr-UN02)#ipcc routed
RP/0/RP0/CPU0:ios(config-lmp-gmpls-uni-nbr-UN02)#
To configure the Access List (ACL), use the ipv4 access-group command at the IPv4 interface in the interface configuration mode.
ipv4 access-group access-list-name { ingress | egress }
| access-list-name |
Access list name. Names cannot contain a space or quotation marks. |
| ingress |
Specifies an inbound interface. |
|
egress |
Specifies an outbound interface. |
No IPv4 access list is defined.
Interface configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
Use the ipv4 access-list command to configure an IPv4 access list. This command places the system in access list configuration mode, in which the denied or permitted access conditions must be defined with the deny or permit command.
The following examples shows how to configure the Access List at the IPv4 interface in the configuration mode:
interface MgmtEth0/RP0/CPU0/0
ipv4 address 10.1.1.1 255.255.255.0
ipv4 access-group IPV4_ICMP_DENY ingress
ipv4 access-group IPV4_ROUTER_FWD_TELNET_TRAFFIC_DENY egress
Sample Configuration for IPv4 Access Lists
ipv4 access-list IPV4_ICMP_DENY
10 deny icmp any any
20 permit ipv4 any any
!
ipv4 access-list IPV4_ROUTER_FWD_TELNET_TRAFFIC_DENY
10 deny tcp any any eq telnet
20 permit ipv4 any any
!
To configure the Access List (ACL), use the ipv6 access-group command at the IPv6 interface in the interface configuration mode.
ipv6 access-group access-list-name { ingress | egress }
| access-list-name |
Access list name. Names cannot contain a space or quotation marks. |
| ingress |
Specifies an inbound interface. |
|
egress |
Specifies an outbound interface. |
No IPv6 access list is defined.
Interface configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
Use the ipv6 access-list command to configure an IPv6access list. This command places the system in access list configuration mode, in which the denied or permitted access conditions must be defined with the deny or permit command.
The following examples shows how to configure the Access List at the IPv6 interface in the configuration mode
interface MgmtEth0/RP0/CPU0/0
ipv6 address 1000::1/64
ipv6 access-group IPV6_SSH_DENY ingress
ipv6 access-group IPV6_ROUTER_FWD_TELNET_TRAFFIC_DENY egress
Sample Configuration for IPv6 Access Lists
ipv6 access-list IPV6_SSH_DENY
10 deny tcp any any eq ssh
20 permit ipv6 any any
!
ipv6 access-list IPV6_ROUTER_FWD_TELNET_TRAFFIC_DENY
10 deny tcp any any eq telnet
20 permit ipv6 any any
!
To specify the keyring name, use the keyring command in the configuration mode.
keyring keyring-name
| keyring-name |
Name of the keyring upto 32 characters. |
None
Configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
The following is a sample in which a keyring is configured.
RP/0/RP0/CPU0:ios#conf
Thu Mar 7 19:33:14.594 UTC
RP/0/RP0/CPU0:ios(config)#keyring kyr1
RP/0/RP0/CPU0:ios(config-keyring-kyr1)#peer peer1
RP/0/RP0/CPU0:ios(config-keyring-kyr1-peer-peer1)#address 10.0.0.1 255.255.255.0
RP/0/RP0/CPU0:ios(config-keyring-kyr1-peer-peer1)#pre-shared-key password 14341B180F547B7977
RP/0/RP0/CPU0:ios(config-keyring-kyr1-peer-peer1)#commit
Thu Mar 7 19:54:33.314 UTC
RP/0/RP0/CPU0:ios(config-keyring-kyr1-peer-peer1)#exit
RP/0/RP0/CPU0:ios(config-keyring-kyr1)#exit
RP/0/RP0/CPU0:ios(config)#exit
RP/0/RP0/CPU0:ios#show keyring kyr1
Thu Mar 7 19:58:07.135 UTC
Keyring Name : kyr1
===============================================================================
Total Peers : 1
-------------------------------------------------------------------------------
Peer Name : peer1
IP Address : 10.0.0.1
Subnet Mask : 255.255.255.0
Local PSK : Configured
Remote PSK : Configured
To configure the LC mode on the OTN-XP card, use the lc-module command in IOS XR configuration mode.
lc-module location location lcmode mode
| location location |
Specifies the location of the optics controller. |
||
| lcmodemode |
Configures the line card mode. The LC modes supported on the OTN-XP card are:
|
None
Cisco IOS XR Configuration
| Release | Modification |
|---|---|
| Release 7.2.1 |
This command was introduced. |
The following is a sample in which the OTN-XP card is configured in the 10G-GREY-MXP mode.
RP/0/RP0/CPU0:ios#configure
Thu Mar 26 21:40:51.495 UTC
RP/0/RP0/CPU0:ios(config)#lc-module location 0/1 lcmode 10G-GREY-MXP
RP/0/RP0/CPU0:ios(config)#commit
To register the device instance with Cisco licensing cloud, use the license smart register idtoken token-id force command.
license smart register idtoken token-id force
|
token_id |
Specifies the token generated in smart manager. |
|
force |
If the registration fails due to communication failure between the device and the portal or satellite, the system waits for 24 hours before attempting to register the device again. Use this option to force the registration. |
None
None
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command was introduced. |
Use this command to register the device instance with Cisco licensing cloud.
The following example registers and sets the token ID required for registration of NCS 1004.
RP/0/RP0/CPU0:ios#license smart register token-id
To manually renew the ID certification or authorization, use the license smart renew command.
license smart renew id{ ID|auth}
|
ID |
ID certificates are renewed automatically after six months. In case, the renewal fails, the product instance goes into unidentified state. You can manually renew the ID certificate using this option. |
|
auth |
Authorization periods are renewed by the Smart Licensing system every 30 days. As long as the license is in an 'Authorized' or 'Out-of-compliance' (OOC), the authorization period is renewed. Use this command to make an on-demand manual update of your registration. Thus, instead of waiting 30 days for the next registration renewal cycle, you can use this option to instantly find out the status of your license. After 90 days, the authorization period expires and the status of the associated licenses display "AUTH EXPIRED". Use this option to retry the authorization period renewal. If the retry is successful, a new authorization period begins. |
None
None
| Release | Modification |
|---|---|
| R7.0.1 |
This command was introduced. |
None
The following example manually renews the ID certificate for NCS 1004.
RP/0/RP0/CPU0:ios#license smart renew id
The following example manually renews the authorization for NCS 1004.
RP/0/RP0/CPU0:ios#license smart renew auth
To cancel the registration of your device, use the license smart deregister command.
license smart deregister
None
None
| Release | Modification |
|---|---|
| R7.0.1 |
This command was introduced. |
When your device is taken off the inventory, shipped elsewhere for redeployment or returned to Cisco for replacement using the return merchandise authorization (RMA) process, you can use this command to cancel the registration on your device. All smart licensing entitlements and certificates on the platform are removed.
The following example deregisters NCS 1004.
RP/0/RP0/CPU0:ios#license smart deregister
To configure the lifetime of IKEv2 security association (SA), use the lifetime command in IKEv2 profile configuration mode.
lifetime seconds
| seconds |
Specifies the lifetime in seconds. The range is from 120 to 86400 seconds. |
None
IKEv2 profile configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
The following is a sample in which an IKEv2 profile is configured.
RP/0/RP0/CPU0:ios#configure
Thu Mar 7 20:00:36.490 UTC
RP/0/RP0/CPU0:ios(config)#ikev2 profile profile1
RP/0/RP0/CPU0:ios(config-ikev2-profile-profile1)#match identity remote address 10.0.0.1 255.255.255.0
RP/0/RP0/CPU0:ios(config-ikev2-profile-profile1)#keyring kyr1
RP/0/RP0/CPU0:ios(config-ikev2-profile-profile1)#lifetime 120
RP/0/RP0/CPU0:ios(config-ikev2-profile-profile1)#commit
Thu Mar 7 20:15:03.401 UTC
RP/0/RP0/CPU0:ios(config-ikev2-profile-profile1)#exit
RP/0/RP0/CPU0:ios(config)#exit
RP/0/RP0/CPU0:ios#show ikev2 profile profile1
Thu Mar 7 20:15:25.776 UTC
Profile Name : profile1
===============================================================================
Keyring : kyr1
Lifetime(Sec) : 120
DPD Interval(Sec) : 10
DPD Retry Interval(Sec) : 2
Match ANY : NO
Total Match remote peers : 1
Addr/Prefix : 10.0.0.1/255.255.255.0
To specify the local optical interface address for an LMP link for a GMPLS UNI controller, use the link-id ipv4 unicast command in GMPLS-UNI controller configuration mode.
link-id ipv4 unicast address
| address |
Specifies the optical unicast IPv4 address. |
None
LMP GMPLS-UNI controller configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
The following example shows how to specify the local optical interface address for an LMP link.
RP/0/RP0/CPU0:ios(config)#lmp
RP/0/RP0/CPU0:ios(config-lmp)#gmpls optical-uni
RP/0/RP0/CPU0:ios(config-lmp-gmpls-uni)#controller Optics0/0/0/0
RP/0/RP0/CPU0:ios(config-lmp-gmpls-uni-ctrl)#link-id ipv4 unicast 11.1.1.1
RP/0/RP0/CPU0:ios(config-lmp-gmpls-uni-ctrl)#
To enable functionality for GMPLS UNI LMP and enter LMP configuration commands, use the lmp command in global configuration mode.
lmp
| This command has no keywords or arguments. |
None
Global configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
The following example shows how to enable LMP functionality and enter the sub-mode for LMP configuration commands.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#lmp
RP/0/RP0/CPU0:ios(config-lmp)#
To specify the IP address of the local node, use the match address local command in the IKEv2 policy configuration mode.
match address local ipv4-address
| ipv4-address |
IP address of the local node. |
None
IKEv2 policy configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
The following is a sample in which an IKEv2 policy is configured.
RP/0/RP0/CPU0:ios#configure
Thu Mar 7 19:26:45.752 UTC
RP/0/RP0/CPU0:ios(config)#ikev2 policy mypolicy
RP/0/RP0/CPU0:ios(config-ikev2-policy-mypolicy)#proposal proposal1
RP/0/RP0/CPU0:ios(config-ikev2-policy-mypolicy)#match address local 10.0.0.1
RP/0/RP0/CPU0:ios(config-ikev2-policy-mypolicy)#commit
Thu Mar 7 19:29:25.043 UTC
RP/0/RP0/CPU0:ios(config-ikev2-policy-mypolicy)#exit
RP/0/RP0/CPU0:ios(config)#exit
RP/0/RP0/CPU0:ios#show ikev2 policy mypolicy
Thu Mar 7 19:30:30.343 UTC
Policy Name : mypolicy
===============================================================================
Total number of match local addr : 1
Match address local : 10.0.0.1
-------------------------------------------------------------------------------
Total number of proposal attached : 1
Proposal Name : proposal1
To specify the IP address of the remote node, use the match identity remote address command in IKEv2 profile configuration mode.
match identity remote address { ipv4-address [ subnet-mask]}
| ipv4-address |
IP address of the remote node. |
| subnet-mask |
Subnet mask address. |
None
IKEv2 profile configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
The following is a sample in which an IKEv2 profile is configured.
RP/0/RP0/CPU0:ios#configure
Thu Mar 7 20:00:36.490 UTC
RP/0/RP0/CPU0:ios(config)#ikev2 profile profile1
RP/0/RP0/CPU0:ios(config-ikev2-profile-profile1)#match identity remote address 10.0.0.1 255.255.255.0
RP/0/RP0/CPU0:ios(config-ikev2-profile-profile1)#keyring kyr1
RP/0/RP0/CPU0:ios(config-ikev2-profile-profile1)#lifetime 120
RP/0/RP0/CPU0:ios(config-ikev2-profile-profile1)#commit
Thu Mar 7 20:15:03.401 UTC
RP/0/RP0/CPU0:ios(config-ikev2-profile-profile1)#exit
RP/0/RP0/CPU0:ios(config)#exit
RP/0/RP0/CPU0:ios#show ikev2 profile profile1
Thu Mar 7 20:15:25.776 UTC
Profile Name : profile1
===============================================================================
Keyring : kyr1
Lifetime(Sec) : 120
DPD Interval(Sec) : 10
DPD Retry Interval(Sec) : 2
Match ANY : NO
Total Match remote peers : 1
Addr/Prefix : 10.0.0.1/255.255.255.0
To specify the neighbor's optical interface ID of an LMP link for a GMPLS UNI controller, use the neighbor interface-id unnumbered command in GMPLS-UNI controller configuration mode.
neighbor interface-id unnumbered interface-id
| interface-id |
Specifies the optical interface ID of the neighbor. |
None
LMP GMPLS-UNI controller configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
The following example shows how to specify the optical interface ID of an LMP neighbor.
RP/0/RP0/CPU0:ios(config)#lmp
RP/0/RP0/CPU0:ios(config-lmp)#gmpls optical-uni
RP/0/RP0/CPU0:ios(config-lmp-gmpls-uni)#controller Optics0/0/0/0
RP/0/RP0/CPU0:ios(config-lmp-gmpls-uni-ctrl)#neighbor interface-id unnumbered 2130706976
RP/0/RP0/CPU0:ios(config-lmp-gmpls-uni-ctrl)#
To specify the neighbor's optical address of an LMP link for a GMPLS UNI controller, use the neighbor link-id ipv4 unicast command in GMPLS-UNI controller configuration mode.
neighbor link-id ipv4 unicast address
| address |
Specifies the IPv4 address of the neighbor. |
None
LMP GMPLS-UNI controller configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
The following example shows how to specify the optical IPv4 address (10.1.1.1) of an LMP neighbor for controller 0/0/0/0:
RP/0/RP0/CPU0:ios(config)#lmp
RP/0/RP0/CPU0:ios(config-lmp)#gmpls optical-uni
RP/0/RP0/CPU0:ios(config-lmp-gmpls-uni)#controller Optics0/0/0/0
RP/0/RP0/CPU0:ios(config-lmp-gmpls-uni-ctrl)#neighbor link-id ipv4 unicast 10.1.1.1
RP/0/RP0/CPU0:ios(config-lmp-gmpls-uni-ctrl)#
To specify an LMP neighbor for GMPLS and enter commands to configure the neighbor, use the neighbor command in the LMP GMPLS-UNI configuration mode.
neighbor name
| name |
Specifies the name of the LMP neighbor. |
None
LMP GMPLS-UNI configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
Under the LMP GMPLS UNI submode, this command creates a submode in which other properties of the neighbor can be specified.
The following example shows how to specify the neighbor UN01 for the GMPLS-UNI controller 0/0/0/0.
RP/0/RP0/CPU0:ios(config)#lmp
RP/0/RP0/CPU0:ios(config-lmp)#gmpls optical-uni
RP/0/RP0/CPU0:ios(config-lmp-gmpls-uni)#neighbor UN01
RP/0/RP0/CPU0:ios(config-lmp-gmpls-uni-nbr-UN01)#exit
RP/0/RP0/CPU0:ios(config-lmp-gmpls-uni)#controller Optics0/0/0/0
RP/0/RP0/CPU0:ios(config-lmp-gmpls-uni-cntl)#neighbor UN01
RP/0/RP0/CPU0:ios(config-lmp-gmpls-uni-cntl)#
To configure an OTNSec policy, use the otnsec policy command in the configuration mode.
otnsec policy policy-name
| policy-name |
Policy name |
None
Configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
The following is a sample in which an OTNSec policy is configured.
RP/0/RP0/CPU0:ios#configure
Mon Mar 11 15:16:58.417 UTC
RP/0/RP0/CPU0:ios(config)#otnsec policy otnsec-policy1
RP/0/RP0/CPU0:ios(config-otnsec-policy)#cipher-suite AES-GCM-256
RP/0/RP0/CPU0:ios(config-otnsec-policy)#security-policy must-secure
RP/0/RP0/CPU0:ios(config-otnsec-policy)#sak-rekey-interval 120
RP/0/RP0/CPU0:ios(config-otnsec-policy)#commit
The following is a sample of an OTNSec policy.
RP/0/RP0/CPU0:ios#show run otnsec policy otnsec-policy1
Tue Mar 12 11:14:03.591 UTC
otnsec policy otnsec-policy1
cipher-suite AES-GCM-256
security-policy must-secure
sak-rekey-interval 120
!
To specify a path option for a GMPLS UNI tunnel, use the path-option command in GMPLS UNI controller tunnel-properties configuration sub-mode.
path-option 10 { no-ero | explicit { name path-name | index index } } [ xro-attribute-set name ] [lockdown] [verbatim]
| 10 |
Specifies the path option index. 10 is the only supported index |
| explicit |
Specifies that LSP paths are IP explicit paths. |
|
name path-name |
Specifies the path name of the IP explicit path. |
|
no-ero |
Specifies that no ERO object is included in signalling. |
|
xro-attribute-set |
(Optional) Specifies the xro attribute set for the path option. |
|
name |
Specifies the name of the xro-attribute-set. |
|
lockdown |
(Optional) Indicates that the tunnel does not reoptimize without user intervention. |
|
verbatim |
(Optional) Bypasses the topology check for explicit paths. |
None
GMPLS UNI controller tunnel-properties configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
The following example shows how to specify the tunnel path option for controller 0/0/0/0, attribute set A01..
RP/0/RP0/CPU0:ios(config)#mpls traffic-eng
RP/0/RP0/CPU0:ios(config-mpls-te)#gmpls optical-uni
RP/0/RP0/CPU0:ios(config-te-gmpls)#controller Optics0/0/0/0
RP/0/RP0/CPU0:ios(config-te-gmpls-cntl)#tunnel-properties
RP/0/RP0/CPU0:ios(config-te-gmpls-tun)#path-option 10 no-ero xro-attribute-set A01 lockdown
RP/0/RP0/CPU0:ios(config-te-gmpls-tun)#
To specify the peer node during keyring configuration, use the peer command in keyring configuration mode.
peer peer-name
| peer-name |
Peer node name. |
None
Keyring configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
The following is a sample in which a keyring is configured.
RP/0/RP0/CPU0:ios#conf
Thu Mar 7 19:33:14.594 UTC
RP/0/RP0/CPU0:ios(config)#keyring kyr1
RP/0/RP0/CPU0:ios(config-keyring-kyr1)#peer peer1
RP/0/RP0/CPU0:ios(config-keyring-kyr1-peer-peer1)#address 10.0.0.1 255.255.255.0
RP/0/RP0/CPU0:ios(config-keyring-kyr1-peer-peer1)#pre-shared-key key1|clear
RP/0/RP0/CPU0:ios(config-keyring-kyr1-peer-peer1)#commit
Thu Mar 7 19:54:33.314 UTC
RP/0/RP0/CPU0:ios(config-keyring-kyr1-peer-peer1)#exit
RP/0/RP0/CPU0:ios(config-keyring-kyr1)#exit
RP/0/RP0/CPU0:ios(config)#exit
RP/0/RP0/CPU0:ios#show keyring kyr1
Thu Mar 7 19:58:07.135 UTC
Keyring Name : kyr1
===============================================================================
Total Peers : 1
-------------------------------------------------------------------------------
Peer Name : peer1
IP Address : 10.0.0.1
Subnet Mask : 255.255.255.0
Local PSK : Configured
Remote PSK : Configured
To specify the trustpoints for use with the RSA signature authentication method, use the pki trustpoint command in IKEv2 profile configuration mode
pki trustpoint trustpoint-label
| trustpoint-label | Specifies the name of the trustpoint. |
None
IKEv2 profile configuration
| Release | Modification |
|---|---|
| R7.2.1 |
This command was introduced. |
The following example shows how to specify the authentication mode in the IKEv2 profile.
RP/0/RP0/CPU0:ios#configure
Thu May 7 16:22:33.804 IST
RP/0/RP0/CPU0:ios(config)#ikev2 profile IP1
RP/0/RP0/CPU0:ios(config-ikev2-profile-IP1)#match identity remote address 1.1.1.2
255.255.255.255
RP/0/RP0/CPU0:ios(config-ikev2-profile-IP1)#pki trustpoint myca
RP/0/RP0/CPU0:ios(config-ikev2-profile-IP1)#lifetime 120
RP/0/RP0/CPU0:ios(config-ikev2-profile-IP1)#authentication local rsa-signature
RP/0/RP0/CPU0:ios(config-ikev2-profile-IP1)#authentication remote rsa-signature
RP/0/RP0/CPU0:ios(config-ikev2-profile-IP1)#commit
To configure the performance monitoring parameters of the optics, Ethernet, and coherent DSP controllers, use the pm command in the controller configuration mode.
pm [ 15-min | 30-sec | 24-hour] [ optics | ether | pcs | fec | otn] [ report | threshold] value
|
15-min | 30-sec | 24-hour |
Configures performance monitoring parameters for 15 minute or 30 second or 24 hour intervals. |
|
optics | ether | pcs | fec | otn |
Specifies whether to configure performance monitoring parameters for the optics, Ethernet, or coherent DSP controllers. |
|
report |
Configures optics TCA reporting status. |
|
threshold |
Configures threshold on optics parameters. |
|
value |
Value of the reporting or threshold parameters. |
None
Controller configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command was introduced. |
The following table describes the optics PM parameters.
|
Parameter |
Description |
|---|---|
|
cd |
Chromatic dispersion TCA reporting status or threshold |
|
dgd |
Differential group delay TCA reporting status or threshold |
|
lbc |
lbc TCA reporting status or threshold |
|
lbc-pc |
lbc percentage TCA reporting status or threshold |
|
low-freq-off |
low signal frequency offset TCA reporting status or threshold |
|
opr |
opr/opr-dbm TCA reporting status or threshold |
|
opt |
opt/opt-dbm TCA reporting status or threshold |
|
osnr |
Optical Signal to Noise Ratio TCA reporting status or threshold |
|
pcr |
Polarization Change Rate TCA reporting status or threshold |
|
pdl |
Polarization Dependent Loss TCA reporting status or threshold |
|
pn |
Phase Noise TCA reporting status or threshold |
|
rx-sig-pow |
rx signal power TCA reporting status or threshold |
|
sopmd |
Second Order Polarization Mode Dispersion TCA reporting status or threshold |
The following table describes the OTN PM parameters.
|
Parameter |
Description |
|---|---|
|
ES-NE |
Error seconds in the near end |
|
ESR-NE |
Error seconds ratio in the near end |
|
SES-NE |
Severely error seconds in the near end |
|
SESR-NE |
Severely error seconds ratio in the near end |
|
UAS-NE |
Unavailable seconds in the near end |
|
BBE-NE |
Background block errors in the near end |
|
BBER-NE |
Background block errors ratio in the near end |
|
FC-NE |
Failure counts in the near end |
|
ES-FE |
Error seconds in the far end |
|
ESR-FE |
Error seconds ratio in the far end |
|
SES-FE |
Severely error seconds in the far end |
|
SESR-FE |
Severely error seconds ratio in the far end |
|
UAS-FE |
Unavailable seconds in the far end |
|
BBE-FE |
Background block errors in the far end |
|
BBER-FE |
Background block errors ratio in the far end |
|
FC-FE |
Failure counts in the far end |
The following table describes the Ethernet PM parameters.
|
Parameter |
Description |
|---|---|
|
rx-util |
Bandwidth utilization of port at the ingress side in percentage. |
|
tx-util |
Bandwidth utilization of port at egress side in percentage. |
|
rx-pkt |
Number of received packets |
|
stat-pkt |
Status of received packets |
|
octet-stat |
Total number of octets of data received in the network |
|
oversize-pkt |
Total number of packets received that were longer than 1518 octets and were otherwise well formed |
|
jabber-stats |
Total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets), and had either a bad FCS with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error) |
|
in-64-octets |
Total number of packets received that were 64 octets in length |
|
in-65-127-octets |
Total number of packets received that were between 65 and 127 octets in length |
|
in-128-255-octets |
Total number of packets received that were between 128 and 255 octets in length |
|
in-256-511-octets |
Total number of packets received that were between 256 and 511 octets in length |
|
in-512-1023-octets |
Total number of packets received that were between 512 and 1023 octets in length |
|
in-1024-1518-octets |
Total number of packets received that were between 1024 and 1518 octets in length |
|
in-mcast |
Total number of multicast frames received error-free |
|
in-bcast |
Total number of broadcast frames received error-free |
|
out-bcast |
Total number of broadcast frames transmitted error-free |
|
out-mcast |
Total number of multicast frames transmitted error-free |
|
tx-pkt |
Number of transmitted packets |
|
out-octets |
Total number of octets transmitted out of the interface, including framing characters |
|
ether-stat-multicast-pkt |
Status of multicast packets |
|
ether-stat-broadcast-pkt |
Status of broadcast packets |
|
ether-stat-undersized-pkt |
Number of good packets received that are shorter than 64 bytes. |
| tx-undersized-pkt | Total number of packets transmitted that are shorter than 64 bytes. |
| tx-oversized-pkt | Total number of oversized packets transmitted. |
| tx-fragments | Total number of fragmented packets transmitted. |
| tx-jabber | Total number of Jabber packets transmitted. |
| tx-bad-fcs | Total number of bad FCS packets transmitted. |
|
fcs-err |
A count of frames received on a particular interface that are an integral number of octets in length but do not pass the FCS check. |
|
ifIn-Octets |
Total number of octets received on the interface, including framing characters. |
|
ifIn-errors |
Number of inbound packets that contained errors preventing them from being delivered to a higher-layer protocol. |
|
in-good-bytes |
Total number of good bytes or octets received. |
|
in-good-pkts |
Total number of good packets received. |
|
long-frame |
A count of frames received on a particular interface that exceed the maximum permitted frame size. |
|
out-good-bytes |
Total number of good bytes or octets transmitted |
|
out-good-pkts |
Total number of good packets transmitted. |
|
1024-1518-octets |
Total number of packets (including error packets) received that were between 1024 and 1518 octets in length inclusive (excluding framing bits but including FCS octets). |
|
128-255-octets |
Total number of packets (including error packets) received that were between 128 and 255 octets in length inclusive (excluding framing bits but including FCS octets). |
|
256-511-octets |
Total number of packets (including error packets) received that were between 256 and 511 octets in length inclusive (excluding framing bits but including FCS octets). |
|
512-1023-octets |
Total number of packets (including error packets) received that were between 512 and 1023 octets in length inclusive (excluding framing bits but including FCS octets). |
|
64-octets |
Total number of packets (including bad packets) received that were 64 octets in length (excluding framing bits but including FCS octets). |
|
65-127-octets |
Total number of packets (including error packets) received that were between 65 and 127 octets in length inclusive (excluding framing bits but including FCS octets). |
The following table describes the FEC PM parameters.
|
Parameter |
Description |
|---|---|
|
ec-words |
Number of bit errors that are corrected by the system |
|
uc-words |
Number of words that are not corrected by the system |
The following table describes the PCS PM parameters.
|
Parameter |
Description |
|---|---|
|
PCS-ES |
Error seconds |
|
PCS-SES |
Severly error seconds |
|
PCS-UAS |
Unavailable seconds |
|
PCS-ES-FE |
Error seconds in far end |
|
PCS-SES-FE |
Severly error seconds in far end |
|
PCS-UAS-FE |
Unavailable seconds in far end |
The following is a sample in which the performance monitoring parameters of optics controller is configured in 24 hour intervals.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller optics 0/0/1/1 pm 24-hour optics threshold osnr max 345
RP/0/RP0/CPU0:ios(config)#commit
The following is a sample in which the performance monitoring parameters of the ethernet controller is configured in 15 minute intervals.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller HundredGigECtrlr 0/3/0/2 pm 15-min pcs report bip enable
RP/0/RP0/CPU0:ios(config)#commit
The following is a sample in which performance monitoring parameters of Coherent DSP controller is configured in 30 second intervals.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller coherentDSP 0/0/1/1 pm 30-sec fec threshold post-fec-ber max OE-15
RP/0/RP0/CPU0:ios(config)#commit
To configure the pre-shared keys for authentication, use the pre-shared-key command in keyring configuration mode.
pre-shared-key{{ key } { clear cleartext-key } { local local-key } { password encrypted-key }}
| key |
Pre-shared key in clear text for the peer node. |
| clear cleartext-key |
Stores the key in clear text. |
| password encrypted-key |
Stores the key as a type-7 encrypted password. |
|
local local-key |
Specifies the pre-shared key for the local node. |
None
Keyring configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
The following is a sample in which a keyring is configured.
RP/0/RP0/CPU0:ios#conf
Thu Mar 7 19:33:14.594 UTC
RP/0/RP0/CPU0:ios(config)#keyring kyr1
RP/0/RP0/CPU0:ios(config-keyring-kyr1)#peer peer1
RP/0/RP0/CPU0:ios(config-keyring-kyr1-peer-peer1)#address 10.0.0.1 255.255.255.0
RP/0/RP0/CPU0:ios(config-keyring-kyr1-peer-peer1)#pre-shared-key password 14341B180F547B7977
RP/0/RP0/CPU0:ios(config-keyring-kyr1-peer-peer1)#commit
Thu Mar 7 19:54:33.314 UTC
RP/0/RP0/CPU0:ios(config-keyring-kyr1-peer-peer1)#exit
RP/0/RP0/CPU0:ios(config-keyring-kyr1)#exit
RP/0/RP0/CPU0:ios(config)#exit
RP/0/RP0/CPU0:ios#show keyring kyr1
Thu Mar 7 19:58:07.135 UTC
Keyring Name : kyr1
===============================================================================
Total Peers : 1
-------------------------------------------------------------------------------
Peer Name : peer1
IP Address : 10.0.0.1
Subnet Mask : 255.255.255.0
Local PSK : Configured
Remote PSK : Configured
To specify the Pseudo-Random Function (PRF) algorithm type, use the prf command in IKEv2 proposal configuration mode.
prf prf-algorithm
| prf-algorithm |
PRF algorithm type. The possible values are sha-1, sha-256, sha-384, and sha-512. |
None
IKEv2 proposal configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
The following is a sample in which an IKEv2 proposal is configured.
RP/0/RP0/CPU0:ios#configure
Thu Mar 7 19:19:30.259 UTC
RP/0/RP0/CPU0:ios(config)#ikev2 proposal proposal1
RP/0/RP0/CPU0:ios(config-ikev2-proposal-proposal1)#encryption aes-cbc-256
RP/0/RP0/CPU0:ios(config-ikev2-proposal-proposal1)#integrity sha-1
RP/0/RP0/CPU0:ios(config-ikev2-proposal-proposal1)#prf sha-256
RP/0/RP0/CPU0:ios(config-ikev2-proposal-proposal1)#dh 20
RP/0/RP0/CPU0:ios(config-ikev2-proposal-proposal1)#commit
Thu Mar 7 19:20:30.916 UTC
RP/0/RP0/CPU0:ios(config-ikev2-proposal-proposal1)#exit
RP/0/RP0/CPU0:ios(config)#exit
RP/0/RP0/CPU0:ios#show ikev2 proposal proposal1
Thu Mar 7 19:20:48.929 UTC
Proposal Name : proposal1
=====================================================================================
Status : Complete
-------------------------------------------------------------------------------------
Total Number of Enc. Alg. : 1
Encr. Alg. : CBC-AES-256
-------------------------------------------------------------------------------------
Total Number of Hash. Alg. : 1
Hash. Alg. : SHA 1
-------------------------------------------------------------------------------------
Total Number of PRF. Alg. : 1
PRF. Alg. : SHA 256
-------------------------------------------------------------------------------------
Total Number of DH Group : 1
DH Group : Group 20
To configure the LMP unicast or neighbor router ID for GMPLS, use the router-id command in the LMP GMPLS UNI configuration or LMP GMPLS UNI neighbor configuration mode.
router-id ipv4 unicast address
| address |
Specifies the GMPLS UNI optical router-id (IPv4 address). |
None
LMP GMPLS UNI configuration
LMP GMPLS UNI neighbor configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
The following example shows how to specify a router ID (address 10.10.4.4) for GMPLS UNI.
RP/0/RP0/CPU0:ios(config)#lmp
RP/0/RP0/CPU0:ios(config-lmp)#gmpls optical-uni
RP/0/RP0/CPU0:ios(config-lmp-gmpls-uni)#router-id ipv4 unicast 10.10.4.4
RP/0/RP0/CPU0:ios(config-lmp-gmpls-uni)
The following example shows how to specify the neighbor router ID 10.10.5.5 for GMPLS UNI.
RP/0/RP0/CPU0:ios(config)#lmp
RP/0/RP0/CPU0:ios(config-lmp)#gmpls optical-uni
RP/0/RP0/CPU0:ios(config-lmp-gmpls-uni)#neighbor UN01
RP/0/RP0/CPU0:ios(config-lmp-gmpls-uni-nbr-UN01)#router-id ipv4 unicast 10.10.5.5
RP/0/RP0/CPU0:ios(config-lmp-gmpls-uni-nbr-UN01)#
To configure the key lifetime for the child security associations (SA), use the sak-rekey-interval command in OTNSec policy configuration mode.
sak-rekey-interval seconds
| seconds |
SAK rekey timer in seconds. The range is from 30 to 1209600 seconds. |
None
OTNSec policy configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
The following is a sample in which an OTNSec policy is configured.
RP/0/RP0/CPU0:ios#configure
Mon Mar 11 15:16:58.417 UTC
RP/0/RP0/CPU0:ios(config)#otnsec policy otnsec-policy1
RP/0/RP0/CPU0:ios(config-otnsec-policy)#cipher-suite AES-GCM-256
RP/0/RP0/CPU0:ios(config-otnsec-policy)#security-policy must-secure
RP/0/RP0/CPU0:ios(config-otnsec-policy)#sak-rekey-interval 120
RP/0/RP0/CPU0:ios(config-otnsec-policy)#commit
The following is a sample of an OTNSec policy.
RP/0/RP0/CPU0:ios#show run otnsec policy otnsec-policy1
Tue Mar 12 11:14:03.591 UTC
otnsec policy otnsec-policy1
cipher-suite AES-GCM-256
security-policy must-secure
sak-rekey-interval 120
!
To specify the security for OTNSec policy, use the security-policy command in OTNSec policy configuration mode.
security-policy must-secure
| must-secure |
Mandatory security for OTNSec. |
None
OTNSec policy configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
The following is a sample in which an OTNSec policy is configured.
RP/0/RP0/CPU0:ios#configure
Mon Mar 11 15:16:58.417 UTC
RP/0/RP0/CPU0:ios(config)#otnsec policy otnsec-policy1
RP/0/RP0/CPU0:ios(config-otnsec-policy)#cipher-suite AES-GCM-256
RP/0/RP0/CPU0:ios(config-otnsec-policy)#security-policy must-secure
RP/0/RP0/CPU0:ios(config-otnsec-policy)#sak-rekey-interval 120
RP/0/RP0/CPU0:ios(config-otnsec-policy)#commit
The following is a sample of an OTNSec policy.
RP/0/RP0/CPU0:ios#show run otnsec policy otnsec-policy1
Tue Mar 12 11:14:03.591 UTC
otnsec policy otnsec-policy1
cipher-suite AES-GCM-256
security-policy must-secure
sak-rekey-interval 120
!
To configure the session ID for OTNSec on ODU4 controller, use the session-id command in OTNSec configuration mode.
session-id session-id
| session-id |
Session ID. The range is from 1 to 65535. |
None
OTNSec configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
The following is a sample in which OTNSec is configured on ODU4 controllers.
RP/0/RP0/CPU0:ios#configure
Mon Mar 12 12:10:21.374 UTC
RP/0/RP0/CPU0:ios(config)#controller ODU4 0/1/0/0/1
RP/0/RP0/CPU0:ios(config-odu4)#otnsec
RP/0/RP0/CPU0:ios(config-otnsec)#source ipv4 10.0.0.1
RP/0/RP0/CPU0:ios(config-otnsec)#destination ipv4 10.0.0.2
RP/0/RP0/CPU0:ios(config-otnsec)#session-id 9000
RP/0/RP0/CPU0:ios(config-otnsec)#policy otnsec-policy1
RP/0/RP0/CPU0:ios(config-otnsec)#ikev2 profile profile1
RP/0/RP0/CPU0:ios(config-ikev2-profile-profile1)#commit
Mon Mar 12 12:14:17.609 UTC
RP/0/RP0/CPU0:ios(config-ikev2-profile-profile1)#exit
RP/0/RP0/CPU0:ios(config)#exit
The following is a running configuration on an ODU4 controller.
RP/0/RP0/CPU0:ios#show run controller ODU4 0/1/0/0/1
Tue Mar 12 12:20:49.153 UTC
controller ODU40/1/0/0/1
gcc2
otnsec
policy otnsec-policy1
source ipv4 10.0.0.1
destination ipv4 10.0.0.2
session-id 9000
!
!
To display alarms in brief or detail, use the show alarms command in XR EXEC mode or Administration EXEC mode.
show alarms brief [card [ location location ] | rack | system ] [ active | history ] ]
show alarms detail [card [ location location ]| rack | system ] [ active | clients | history | stats ] ]
| brief |
Displays alarms in brief. |
| card |
Displays card scope alarms related data. |
| rack |
Displays rack scope alarms related data. |
| system |
Displays system scope alarms related data. |
| location location |
Specifies the target location in the rack/slot notation. |
| active |
Displays active alarms. |
| history |
Displays alarm history. |
| detail |
Displays alarms in detail. |
| clients |
Displays clients associated with the service. |
| stats |
Displays service statistics. |
None
XR EXEC
Administration EXEC
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command was introduced. |
This command displays the alarms in brief or detail. The command displays only the administration alarms in admin EXEC mode and all the alarms in XR EXEC mode.
The following example shows the output of the show alarms command.
sysadmin-vm:0_RP0# show alarms
Wed Mar 20 05:25:53.146 UTC+00:00
-----------------------------------------------------------------------------------------------
Active Alarms
-----------------------------------------------------------------------------------------------
Location Severity Group Set time Description
------------------------------------------------------------------------------------------------
0/PM0 major environ 03/19/19 21:37:29 Power Module Output Disabled
0 major environ 03/19/19 21:37:35 Power Module redundancy lost.
Wed Mar 20 05:26:52.116 UTC
-------------------------------------------------------------------------------------------------------
Active Alarms
-------------------------------------------------------------------------------------------------------
Location Severity Group Set Time Description
-------------------------------------------------------------------------------------------------------
0/PM0 Major FPD_Infra 03/19/2019 21:39:04 UTC One Or More FPDs Need Upgrade
Or Not In Current State
To display status and configuration information about the interfaces on a specific node, use the show controllers command in XR EXEC mode.
show controllers controllertype R/S/I/P [ pm { current | history } { 30 sec | 15-min | 24-hour } { optics | ether | pcs | prbs } linenumber { otn | fec } ]
To view the the bits-per-symbol or baud rate of the optics controller for a specific range use the following command:
show controllers optics R/S/I/P { bps-range bps-range | baud-rate-range baud-range } | include data-rate | include fec-type
| controllertype |
Type of the controller. The possible values are HundredGigECtrlr, CoherentDSP, ODU4, and Optics. |
| R/S/I/P |
Rack/Slot/Instance/Port of the controller. |
| pm |
Displays performance monitoring parameters for the controller. |
| current |
Displays the current performance monitoring data in 30 second, 15 minute, and 24 hour intervals. |
| history |
Displays the historical performance monitoring data in 30 second, 15 minute, and 24 hour intervals. |
| optics | ether | pcs | prbs |
optics to display the PM data for Optics controller, ether, pcs, and prbs to display the PM data for Ethernet controller. |
| linenumber |
Line number to display performance monitoring data. The range is 1 to 4. |
| otn | fec |
Displays OTN PM data or FEC PM data for CoherentDSP controller. |
| bps-range bps-range |
Displays the BPS for the specified range. |
| baud-rate-range baud-range |
Displays the baud rates for the specified range. |
| | include |
Filters the show command output so that it displays only lines that contain a particular regular expression. |
| data-rates |
Data rate for which the BPS or baud rate is displayed. |
| fec-type |
FEC type for which the BPS or baud rate is displayed. |
The following table describes the PRBS parameters.
|
Parameter |
Description |
|---|---|
|
EBC |
Cumulative count of PRBS bit errors in the sampling window (15 min or 24 hour). Bit errors are accumulated only if PRBS signal is locked. |
|
FOUND-COUNT |
Number of state transitions from signal unlocked state to locked state in the sampling window. If no state change is observed in the interval, the count will be zero. |
|
LOST-COUNT |
Number of state transitions from signal locked state to signal unlocked state in the sampling window. If there is no state change observed in the interval, the count will be zero. |
|
FOUND-AT-TS |
Latest timestamp when the PRBS state switches from unlocked state to locked state in the sampling window. If no state change is observed in the sampling window, this value will be null. |
|
LOST-AT-TS |
Latest timestamp when the PRBS state switches from locked state to unlocked state in the sampling window. If no state change is observed in the sampling window, this value will be null. |
|
CONFIG-PTRN |
Configured PRBS pattern on the port. |
Total TX Power and Total RX Power: For multi-lane controller optics, total power is calculated by converting each lane power value from dBm to mW, and adding each lane power. Total power in mW must then be converted to dBm.
Total power in mW = [(Lane 1 power in mW) + (Lane 2 power in mW) + (Lane 3 power in mW) + (Lane 4 power in mW)]
Total power in dBm = Converted value of total power in mW to dBm
The status and configuration information of all the interfaces is displayed.
XR EXEC
| Release | Modification |
|---|---|
| 7.0.1 |
This command was introduced. |
|
7.1.1 |
pcs keyword was added. |
The following is a sample to view the laser squlech status on the ethernet controller.
RP/0/RP0/CPU0:ios#show controller HundredGigECtrlr 0/1/0/10
RP/0/RP0/CPU0:ios#show controller HundredGigECtrlr 0/1/0/10
Fri Feb 22 15:18:47.011 UTC
Operational data for interface HundredGigECtrlr0/1/0/10:
State:
Administrative state: enabled
Operational state: Up
LED state: Green On
Maintenance: Disabled
AINS Soak: None
Total Duration: 0 hour(s) 0 minute(s)
Remaining Duration: 0 hour(s) 0 minute(s) 0 second(s)
Laser Squelch: Enabled
Phy:
Media type: Not known
Statistics:
FEC:
Corrected Codeword Count: 0
Uncorrected Codeword Count: 0
Autonegotiation disabled.
Operational values:
Speed: 100Gbps
Duplex: Full Duplex
Flowcontrol: None
Loopback: None (or external)
BER monitoring:
Not supported
Forward error correction: Standard (Reed-Solomon)
Holdoff Time: 0ms
The following is a sample to view the hold off timer configured on the ethernet controller.
RP/0/RP0/CPU0:ios#show controller HundredGigECtrlr 0/1/0/10
Fri Feb 22 18:58:06.888 UTC
Operational data for interface HundredGigECtrlr0/1/0/10:
State:
Administrative state: enabled
Operational state: Up
LED state: Green On
Maintenance: Disabled
AINS Soak: None
Total Duration: 0 hour(s) 0 minute(s)
Remaining Duration: 0 hour(s) 0 minute(s) 0 second(s)
Laser Squelch: Enabled
Phy:
Media type: Not known
Statistics:
FEC:
Corrected Codeword Count: 0
Uncorrected Codeword Count: 0
Autonegotiation disabled.
Operational values:
Speed: 100Gbps
Duplex: Full Duplex
Flowcontrol: None
Loopback: None (or external)
BER monitoring:
Not supported
Forward error correction: Standard (Reed-Solomon)
Holdoff Time: 3000ms
The following is a sample to view the loopback configured on the ethernet controller.
RP/0/RP0/CPU0:ios#show controller HundredGigECtrlr 0/1/0/10
Fri Feb 22 20:01:00.521 UTC
Operational data for interface HundredGigECtrlr0/1/0/10:
State:
Administrative state: enabled
Operational state: Up
LED state: Green On
Maintenance: Enabled
AINS Soak: Pending
Total Duration: 0 hour(s) 30 minute(s)
Remaining Duration: 0 hour(s) 30 minute(s) 0 second(s)
Laser Squelch: Enabled
Phy:
Media type: Not known
Statistics:
FEC:
Corrected Codeword Count: 0
Uncorrected Codeword Count: 6
Autonegotiation disabled.
Operational values:
Speed: 100Gbps
Duplex: Full Duplex
Flowcontrol: None
Loopback: Line
BER monitoring:
Not supported
Forward error correction: Standard (Reed-Solomon)
Holdoff Time: 0ms
The following example displays the optics controller statistics with AINS Soak in running state.
RP/0/RP0/CPU0:ios#show controller optics 0/1/0/3
Thu Feb 21 19:45:41.088 UTC
Controller State: Up
Transport Admin State: Automatic In Service
Laser State: On
LED State: Green
Optics Status
Optics Type: Grey optics
Alarm Status:
-------------
Detected Alarms: None
LOS/LOL/Fault Status:
Alarm Statistics:
-------------
HIGH-RX-PWR = 0 LOW-RX-PWR = 0
HIGH-TX-PWR = 0 LOW-TX-PWR = 0
HIGH-LBC = 0 HIGH-DGD = 0
OOR-CD = 0 OSNR = 0
WVL-OOL = 0 MEA = 0
IMPROPER-REM = 0
TX-POWER-PROV-MISMATCH = 0
Performance Monitoring: Enable
THRESHOLD VALUES
----------------
Parameter High Alarm Low Alarm High Warning Low Warning
------------------------ ---------- --------- ------------ -----------
Rx Power Threshold(dBm) 4.9 -12.0 0.0 0.0
Tx Power Threshold(dBm) 3.5 -10.1 0.0 0.0
LBC Threshold(mA) N/A N/A 0.00 0.00
LBC High Threshold = 98 %
Polarization parameters not supported by optics
Total TX Power = 6.39 dBm
Total RX Power = 5.85 dBm
Lane Laser Bias TX Power RX Power Output Frequency
---- ---------- ---------- ---------- ----------------
1 75.0 % 0.59 dBm 0.63 dBm 230.43 THz
2 68.6 % 0.06 dBm -0.68 dBm 230.43 THz
3 69.0 % 0.26 dBm -0.63 dBm 230.43 THz
4 69.1 % 0.56 dBm -0.10 dBm 230.43 THz
Transceiver Vendor Details
Form Factor : QSFP28
Name : CISCO-FINISAR
Part Number : FTLC1152RGPL-C2
Rev Number : CISCO-FINISAR
Serial Number : FNS22150LEC
PID : QSFP-100G-CWDM4-S
VID : V02
CISCO-FINISAR
Date Code(yy/mm/dd) : 18/04/11
Fiber Connector Type: LC
Sonet Application Code: Not Set
Ethernet Compliance Code: 100GBASE-CWDM4
Transceiver Temperature : 32 Celsius
AINS Soak : Running
AINS Timer : 0h, 15m
AINS remaining time : 771 seconds
The following is a sample to view the current performance monitoring parameters of the optics controller in 15 minute intervals.
RP/0/RP0/CPU0:ios#show controller optics 0/1/0/3 pm current 15-min optics 3
Sat Feb 9 19:33:42.480 UTC
Optics in the current interval [19:30:00 - 19:33:42 Sat Feb 9 2019]
Optics current bucket type : Valid
MIN AVG MAX Operational Configured TCA Operational Configured TCA
Threshold(min) Threshold(min) (min) Threshold(max) Threshold(max) (max)
LBC[% ] : 0.0 0.0 0.0 0.0 NA NO 100.0 NA NO
OPT[dBm] : -40.00 -40.00 -40.00 -30.00 NA NO 63.32 NA NO
OPR[dBm] : -40.00 -40.00 -40.00 -30.00 NA NO 63.32 NA NO
FREQ_OFF[Mhz]: 0 0 0 0 NA NO 0 NA NO
The following is a sample to view the current performance monitoring parameters of the Coherent DSP controller in 15 minute intervals.
RP/0/RP0/CPU0:ios#show controller coherentDSP 0/2/0/1 pm current 15-min fec
Sat Feb 9 11:23:42.196 UTC
g709 FEC in the current interval [11:15:00 - 11:23:42 Sat Feb 9 2019]
FEC current bucket type : Valid
EC-BITS : 291612035786 Threshold : 903330 TCA(enable) : YES
UC-WORDS : 0 Threshold : 5 TCA(enable) : YES
MIN AVG MAX Threshold TCA Threshold TCA
(min) (enable) (max) (enable)
PreFEC BER : 7.1E-03 7.2E-03 8.1E-03 0E-15 NO 0E-15 NO
PostFEC BER : 0E-15 0E-15 0E-15 0E-15 NO 0E-15 NO
The following is a sample of an encryption configuration on an ODU4 controller.
RP/0/RP0/CPU0:ios#show controllers ODU4 0/1/0/0/1 otnsec
Tue Mar 12 17:34:50.660 UTC
Controller Name : ODU4 0/1/0/0/1
Source ip : 10.0.0.1
Destination ip : 10.0.0.2
Session id : 9000
IKEv2 profile : Not Configured
Session State : SECURED
Otnsec policy name : otnsec-policy1
cipher-suite : AES-GCM-256
security-policy : Must Secure
sak-rekey-interval : 120
Time to rekey : 0
Programming Status :
Inbound SA(Rx) :
AN[0] :
SPI : None
Outbound SA(Tx) :
AN[0] :
SPI : None
The following is a sample to view the summary of all the ODU4 controllers.
RP/0/RP0/CPU0:ios#show controller ODU4 * otnsec summary
Tue Mar 12 15:18:26.299 IST
Controller Name Source ip Destination ip Session id Session State
------------------------------------------------------------------------------------------------
ODU4 0/0/0/0/1 1.1.1.1 1.1.1.2 1 SECURED
ODU4 0/0/0/0/2 1.1.1.1 1.1.1.2 2 SECURED
ODU4 0/0/0/0/3 1.1.1.1 1.1.1.2 3 SECURED
ODU4 0/0/0/0/4 1.1.1.1 1.1.1.2 4 SECURED
ODU4 0/0/0/0/5 1.1.1.1 1.1.1.2 5 SECURED
ODU4 0/0/0/1/1 1.1.2.1 1.1.2.2 6 SECURED
ODU4 0/0/0/1/2 1.1.2.1 1.1.2.2 7 SECURED
ODU4 0/0/0/1/3 1.1.2.1 1.1.2.2 8 SECURED
ODU4 0/0/0/1/4 1.1.2.1 1.1.2.2 9 SECURED
ODU4 0/0/0/1/5 1.1.2.1 1.1.2.2 10 SECURED
ODU4 0/1/0/0/1 1.1.3.1 1.1.3.2 11 SECURED
ODU4 0/1/0/0/2 1.1.3.1 1.1.3.2 12 SECURED
ODU4 0/1/0/0/3 1.1.3.1 1.1.3.2 13 SECURED
ODU4 0/1/0/0/4 1.1.3.1 1.1.3.2 14 SECURED
ODU4 0/1/0/0/5 1.1.3.1 1.1.3.2 15 SECURED
ODU4 0/1/0/1/1 1.1.4.1 1.1.4.2 16 SECURED
ODU4 0/1/0/1/2 1.1.4.1 1.1.4.2 17 SECURED
ODU4 0/1/0/1/3 1.1.4.1 1.1.4.2 18 SECURED
ODU4 0/1/0/1/4 1.1.4.1 1.1.4.2 19 SECURED
ODU4 0/1/0/1/5 1.1.4.1 1.1.4.2 20 SECURED
ODU4 0/2/0/0/1 1.1.5.1 1.1.5.2 21 SECURED
ODU4 0/2/0/0/2 1.1.5.1 1.1.5.2 22 SECURED
ODU4 0/2/0/0/3 1.1.5.1 1.1.5.2 23 SECURED
ODU4 0/2/0/0/4 1.1.5.1 1.1.5.2 24 SECURED
ODU4 0/2/0/0/5 1.1.5.1 1.1.5.2 25 SECURED
ODU4 0/2/0/1/1 1.1.6.1 1.1.6.2 26 SECURED
ODU4 0/2/0/1/2 1.1.6.1 1.1.6.2 27 SECURED
ODU4 0/2/0/1/3 1.1.6.1 1.1.6.2 28 SECURED
ODU4 0/2/0/1/4 1.1.6.1 1.1.6.2 29 SECURED
ODU4 0/2/0/1/5 1.1.6.1 1.1.6.2 30 SECURED
ODU4 0/3/0/0/1 1.1.7.1 1.1.7.2 31 SECURED
ODU4 0/3/0/0/2 1.1.7.1 1.1.7.2 32 SECURED
ODU4 0/3/0/0/3 1.1.7.1 1.1.7.2 33 SECURED
ODU4 0/3/0/0/4 1.1.7.1 1.1.7.2 34 SECURED
ODU4 0/3/0/0/5 1.1.7.1 1.1.7.2 35 SECURED
ODU4 0/3/0/1/1 1.1.8.1 1.1.8.2 36 SECURED
ODU4 0/3/0/1/2 1.1.8.1 1.1.8.2 37 SECURED
ODU4 0/3/0/1/3 1.1.8.1 1.1.8.2 38 SECURED
ODU4 0/3/0/1/4 1.1.8.1 1.1.8.2 39 SECURED
ODU4 0/3/0/1/5 1.1.8.1 1.1.8.2 40 SECURED
The following is a sample to view the PM statistics for encryption.
RP/0/RP0/CPU0:ios#show controllers ODU4 0/1/0/0/1 pm current 30-sec otnsec
Tue Mar 12 15:19:33.371 IST
OTNSec in the current interval [15:19:30 - 15:19:33 Tue Mar 12 2019]
OTNSEC current bucket type : Valid
InBlocks : 0 Threshold : 0 TCA(enable) : No
InBlocksEnc : 0 Threshold : 0 TCA(enable) : No
InBlocksUnEncrypted : 0 Threshold : 0 TCA(enable) : No
InBlocksProtected : 0 Threshold : 0 TCA(enable) : No
InBlocksUnProtected : 0 Threshold : 0 TCA(enable) : No
InBlocksSequenceErrors : 0 Threshold : 0 TCA(enable) : No
InBlocksReplayErrors : 0 Threshold : 0 TCA(enable) : No
InBlocksAuthErrors : 0 Threshold : 0 TCA(enable) : No
InBlocksZeroed : 0 Threshold : 0 TCA(enable) : No
OutBlocks : 3425548 Threshold : 0 TCA(enable) : No
OutBlocksEnc : 3425548 Threshold : 0 TCA(enable) : No
OutBlocksUnEncrypted : 0 Threshold : 0 TCA(enable) : No
OutBlocksSequenceErrors: 0 Threshold : 0 TCA(enable) : No
OutBlocksZeroed : 0 Threshold : 0 TCA(enable) : No
Last clearing of "show controllers ODU" counters never
The following is a sample to view the current performance monitoring parameters for the ethernet controller in 30 second intervals.
RP/0/RP0/CPU0:ios#show controllers hundredGigECtrlr 0/0/0/2 pm current 30-sec pcs
Tue Nov 19 09:17:26.684 UTC
Ethernet PCS in the current interval [09:17:00 - 09:17:26 Tue Nov 19 2019]
Ethernet PCS current bucket type : Valid
BIP[00] : 0 Threshold : 0 TCA(enable) : NO
BIP[01] : 0 Threshold : 0 TCA(enable) : NO
BIP[02] : 0 Threshold : 0 TCA(enable) : NO
BIP[03] : 0 Threshold : 0 TCA(enable) : NO
BIP[04] : 0 Threshold : 0 TCA(enable) : NO
BIP[05] : 0 Threshold : 0 TCA(enable) : NO
BIP[06] : 0 Threshold : 0 TCA(enable) : NO
BIP[07] : 0 Threshold : 0 TCA(enable) : NO
BIP[08] : 0 Threshold : 0 TCA(enable) : NO
BIP[09] : 0 Threshold : 0 TCA(enable) : NO
BIP[10] : 0 Threshold : 0 TCA(enable) : NO
BIP[11] : 0 Threshold : 0 TCA(enable) : NO
BIP[12] : 0 Threshold : 0 TCA(enable) : NO
BIP[13] : 0 Threshold : 0 TCA(enable) : NO
BIP[14] : 0 Threshold : 0 TCA(enable) : NO
BIP[15] : 0 Threshold : 0 TCA(enable) : NO
BIP[16] : 0 Threshold : 0 TCA(enable) : NO
BIP[17] : 0 Threshold : 0 TCA(enable) : NO
BIP[18] : 0 Threshold : 0 TCA(enable) : NO
BIP[19] : 0 Threshold : 0 TCA(enable) : NO
FRM-ERR[00] : 0 Threshold : 0 TCA(enable) : NO
FRM-ERR[01] : 0 Threshold : 0 TCA(enable) : NO
FRM-ERR[02] : 0 Threshold : 0 TCA(enable) : NO
FRM-ERR[03] : 0 Threshold : 0 TCA(enable) : NO
FRM-ERR[04] : 0 Threshold : 0 TCA(enable) : NO
FRM-ERR[05] : 0 Threshold : 0 TCA(enable) : NO
FRM-ERR[06] : 0 Threshold : 0 TCA(enable) : NO
FRM-ERR[07] : 0 Threshold : 0 TCA(enable) : NO
FRM-ERR[08] : 0 Threshold : 0 TCA(enable) : NO
FRM-ERR[09] : 0 Threshold : 0 TCA(enable) : NO
FRM-ERR[10] : 0 Threshold : 0 TCA(enable) : NO
FRM-ERR[11] : 0 Threshold : 0 TCA(enable) : NO
FRM-ERR[12] : 0 Threshold : 0 TCA(enable) : NO
FRM-ERR[13] : 0 Threshold : 0 TCA(enable) : NO
FRM-ERR[14] : 0 Threshold : 0 TCA(enable) : NO
FRM-ERR[15] : 0 Threshold : 0 TCA(enable) : NO
FRM-ERR[16] : 0 Threshold : 0 TCA(enable) : NO
FRM-ERR[17] : 0 Threshold : 0 TCA(enable) : NO
FRM-ERR[18] : 0 Threshold : 0 TCA(enable) : NO
FRM-ERR[19] : 0 Threshold : 0 TCA(enable) : NO
BAD-SH[00] : 0 Threshold : 0 TCA(enable) : NO
BAD-SH[01] : 0 Threshold : 0 TCA(enable) : NO
BAD-SH[02] : 0 Threshold : 0 TCA(enable) : NO
BAD-SH[03] : 0 Threshold : 0 TCA(enable) : NO
BAD-SH[04] : 0 Threshold : 0 TCA(enable) : NO
BAD-SH[05] : 0 Threshold : 0 TCA(enable) : NO
BAD-SH[06] : 0 Threshold : 0 TCA(enable) : NO
BAD-SH[07] : 0 Threshold : 0 TCA(enable) : NO
BAD-SH[08] : 0 Threshold : 0 TCA(enable) : NO
BAD-SH[09] : 0 Threshold : 0 TCA(enable) : NO
BAD-SH[10] : 0 Threshold : 0 TCA(enable) : NO
BAD-SH[11] : 0 Threshold : 0 TCA(enable) : NO
BAD-SH[12] : 0 Threshold : 0 TCA(enable) : NO
BAD-SH[13] : 0 Threshold : 0 TCA(enable) : NO
BAD-SH[14] : 0 Threshold : 0 TCA(enable) : NO
BAD-SH[15] : 0 Threshold : 0 TCA(enable) : NO
BAD-SH[16] : 0 Threshold : 0 TCA(enable) : NO
BAD-SH[17] : 0 Threshold : 0 TCA(enable) : NO
BAD-SH[18] : 0 Threshold : 0 TCA(enable) : NO
BAD-SH[19] : 0 Threshold : 0 TCA(enable) : NO
ES : 0 Threshold : 0 TCA(enable) : NO
SES : 0 Threshold : 0 TCA(enable) : NO
UAS : 0 Threshold : 0 TCA(enable) : NO
ES-FE : 0 Threshold : 0 TCA(enable) : NO
SES-FE : 0 Threshold : 0 TCA(enable) : NO
UAS-FE : 0 Threshold : 0 TCA(enable) : NO
Last clearing of "show controllers ETHERNET " counters never
RP/0/RP0/CPU0:ios#
The following is a sample to view the historical performance monitoring parameters for ethernet controller in 30 second intervals.
RP/0/RP0/CPU0:ios#show controllers hundredGigECtrlr 0/0/0/2 pm history 30-sec pcs 1
Tue Nov 19 09:27:49.169 UTC
Ethernet PCS in the current interval [09:27:00 - 09:27:30 Tue Nov 19 2019]
Ethernet PCS current bucket type : Valid
BIP[00] : 0
BIP[01] : 0
BIP[02] : 0
BIP[03] : 0
BIP[04] : 0
BIP[05] : 0
BIP[06] : 0
BIP[07] : 0
BIP[08] : 0
BIP[09] : 0
BIP[10] : 0
BIP[11] : 0
BIP[12] : 0
BIP[13] : 0
BIP[14] : 0
BIP[15] : 0
BIP[16] : 0
BIP[17] : 0
BIP[18] : 0
BIP[19] : 0
FRM-ERR[00] : 0
FRM-ERR[01] : 0
FRM-ERR[02] : 0
FRM-ERR[03] : 0
FRM-ERR[04] : 0
FRM-ERR[05] : 0
FRM-ERR[06] : 0
FRM-ERR[07] : 0
FRM-ERR[08] : 0
FRM-ERR[09] : 0
FRM-ERR[10] : 0
FRM-ERR[11] : 0
FRM-ERR[12] : 0
FRM-ERR[13] : 0
FRM-ERR[14] : 0
FRM-ERR[15] : 0
FRM-ERR[16] : 0
FRM-ERR[17] : 0
FRM-ERR[18] : 0
FRM-ERR[19] : 0
BAD-SH[00] : 0
BAD-SH[01] : 0
BAD-SH[02] : 0
BAD-SH[03] : 0
BAD-SH[04] : 0
BAD-SH[05] : 0
BAD-SH[06] : 0
BAD-SH[07] : 0
BAD-SH[08] : 0
BAD-SH[09] : 0
BAD-SH[10] : 0
BAD-SH[11] : 0
BAD-SH[12] : 0
BAD-SH[13] : 0
BAD-SH[14] : 0
BAD-SH[15] : 0
BAD-SH[16] : 0
BAD-SH[17] : 0
BAD-SH[18] : 0
BAD-SH[19] : 0
ES : 0
SES : 0
UAS : 0
ES-FE : 0
SES-FE : 0
UAS-FE : 0
Last clearing of "show controllers ETHERNET " counters never
RP/0/RP0/CPU0:ios#
The following is a sample to view the Pseudo Random Binary Sequence (PRBS) performance monitoring parameters on the coherentDSP controller.
Mon Feb 13 00:58:48.327 UTC
PRBS in the current interval [00:45:00 - 00:58:48 Mon Feb 13 2019]
PRBS current bucket type : Valid
EBC : 40437528165
FOUND-COUNT : 1 FOUND-AT-TS : 00:51:22 Mon Feb 13 2019
LOST-COUNT : 1 LOST-AT-TS : 00:52:52 Mon Feb 13 2019
CONFIG-PTRN : PRBS_PATTERN_PN31
Last clearing of "show controllers OTU" counters neverTo display the contents of current IPv4 access lists, use the show access-lists ipv4 command in EXEC mode.
show access-lists ipv4 [ interface MgmtEth R/S/I/P | maximum [ detail] | summary [ access-list-name ] | usage pfilter location { location node-id | all } | access-list-name [ sequence-number | usage pfilter location { location node-id | all } ] ]
| R/S/I/P | Rack/Slot/Instance/Port/ number of the interface. |
| access-list-name |
(Optional) Name of a particular IPv4 access list. The name cannot contain a space or quotation mark; it may contain numbers. |
|
location number |
Location of a particular IPv4 access list. |
| locationnode-id |
(Optional) Location of a particular IPv4 access list. The node-id argument is entered in the rack/slot/module notation. |
| usage |
(Optional) Displays the usage of the access list on a given line card. |
| pfilter |
(Optional) Displays the packet filtering usage for the specified line card. |
|
summary |
Displays a summary of all current IPv4 access lists. |
|
sequence-number |
(Optional) Sequence number of a particular IPv4 access list. |
|
maximum |
Displays the current maximum number of configurable IPv4 accesscontrol lists (ACLs) and access control entries (ACEs). |
|
detail |
(Optional) Displays complete out-of-resource (OOR) details. |
|
all |
(Optional) Displays the location of all the line cards. |
Displays all IPv4 access lists.
EXEC
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
Use the show access-lists ipv4 command to display the contents of all IPv4 access lists. To display the contents of a specific IPv4 access list, use the name argument. Use the sequence-number argument to specify the sequence number of the access list.
Use the show access-lists ipv4 summary command to display a summary of all current IPv4 access lists. To display a summary of a specific IPv4 access list, use the name argument.
Use the show access-lists ipv4 maximum detail command to display the OOR details for IPv4 access lists. OOR limits the number of ACLs and ACEs that can be configured in the system. When the limit is reached, configuration of new ACLs or ACEs is rejected.
In the following example, the contents of all IPv4 access lists are displayed:
RP/0/RP0/CPU0:ios# show access-lists ipv4
RP/0/RP0/CPU0:ios#show access-lists ipv4
Wed Jan 17 09:52:12.448 IST
ipv4 access-list IPV4_ICMP_DENY
10 deny icmp any any (8 matches)
20 permit ipv4 any any (106 matches)
ipv4 access-list IPV4_ROUTER_FWD_TELNET_TRAFFIC_DENY
10 deny tcp any any eq telnet (3 matches)
20 permit ipv4 any any (6 matches)
To display the contents of current IPv6 access lists, use the show access-lists ipv6 command in EXEC mode.
show access-lists ipv6 [ interface MgmtEth R/S/I/P | maximum [ detail] | summary [ access-list-name ] | usage pfilter location { location node-id | all } | access-list-name [ sequence-number | usage pfilter location { location node-id | all } ] ]
| R/S/I/P | Rack/Slot/Instance/Port/ number of the interface. |
| access-list-name |
(Optional) Name of a particular IPv4 access list. The name cannot contain a space or quotation mark; it may contain numbers. |
|
location number |
Location of a particular IPv4 access list. |
| location node-id |
(Optional) Location of a particular IPv4 access list. The node-id argument is entered in the rack/slot/module notation. |
| usage |
(Optional) Displays the usage of the access list on a given line card. |
| pfilter |
(Optional) Displays the packet filtering usage for the specified line card. |
|
summary |
Displays a summary of all current IPv4 access lists. |
|
sequence-number |
(Optional) Sequence number of a particular IPv4 access list. |
|
maximum |
Displays the current maximum number of configurable IPv4 accesscontrol lists (ACLs) and access control entries (ACEs). |
|
detail |
(Optional) Displays complete out-of-resource (OOR) details. |
|
all |
(Optional) Displays the location of all the line cards. |
Displays all IPv6 access lists.
EXEC
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
The show access-lists ipv6 command is similar to the show access-lists ipv4 command, except that it is IPv6 specific.
Use the show access-lists ipv6 command to display the contents of all IPv6 access lists. To display the contents of a specific IPv6 access list, use the name argument. Use the sequence-number argument to specify the sequence number of the access list.
Use the show access-lists ipv6 summary command to display a summary of all current IPv6 access lists. To display a summary of a specific IPv6 access list, use the name argument.
Use the show access-lists ipv6 maximum detail command to display the OOR details for IPv6 access lists. OOR limits the number of ACLs and ACEs that can be configured in the system. When the limit is reached, configuration of new ACLs or ACEs is rejected.
In the following example, the contents of all IPv6 access lists are displayed:
RP/0/RP0/CPU0:ios#show access-lists ipv6
Wed Jan 17 09:52:14.591 IST
ipv6 access-list IPV6_ROUTER_FWD_TELNET_TRAFFIC_DENY
10 deny tcp any any eq telnet (3 matches)
20 permit ipv6 any any (5 matches)
ipv6 access-list IPV6_SSH_DENY
10 deny tcp any any eq ssh (9 matches)
20 permit ipv6 any any (100 matches)
To display environmental monitor parameters for the system, use the show environment command in administration EXEC mode.
show environment [ all | fan | power | voltages | current | trace | temperatures ] [ location | location ]
| all |
(Optional) Displays information for all the environmental monitor parameters. |
| fan |
(Optional) Displays information about the fans. |
| power |
(Optional) Displays power supply voltage and current information. |
| voltages |
(Optional) Displays system voltage information. |
| current |
(Optional) Displays current sensor information. |
| temperatures |
(Optional) Displays system temperature information. |
| trace |
(Optional) Displays trace data for environment monitoring. |
| location | location |
(Optional) Enter the location for which the environmental information needs to be displayed. |
All environmental monitor parameters are displayed.
Administration EXEC
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command was introduced. |
The show environment command displays information about the hardware that is installed in the system, including fans, power supply voltage, current information, and temperatures.
The following example shows sample output from the show environment command with the fan keyword.
sysadmin-vm:0_RP0# show environment fan
Wed Mar 20 04:40:02.510 UTC+00:00
=============================================
Fan speed (rpm)
Location FRU Type FAN_0 FAN_1
---------------------------------------------
0/FT0 NCS1K4-FAN 7020 6960
0/FT1 NCS1K4-FAN 6750 6720
0/FT2 NCS1K4-FAN 6750 6720
0/PM0 NCS1K4-AC-PSU 24800 23680
0/PM1 NCS1K4-AC-PSU 14240 14176
The following example shows sample output from the show environment command with the temperatures keyword.
sysadmin-vm:0_RP0# show environment temperatures location 0/RP0
Wed Mar 20 04:40:48.518 UTC+00:00
================================================================================
Location TEMPERATURE Value Crit Major Minor Minor Major Crit
Sensor (deg C) (Lo) (Lo) (Lo) (Hi) (Hi) (Hi)
--------------------------------------------------------------------------------
0/RP0
TEMP_LOCAL 29 -10 -5 0 55 65 70
TEMP_REMOTE1 30 -10 -5 0 55 65 70
TEMP_CPU_DIE 30 -10 -5 0 75 80 90
The following example shows sample output from the show environment command with the power keyword.
sysadmin-vm:0_RP0# show environment power
Wed Mar 20 04:41:39.990 UTC+00:00
================================================================================
CHASSIS LEVEL POWER INFO: 0
================================================================================
Total output power capacity (N + 1) : 2000W + 0W
Total output power required : 1430W
Total power input : 1075W
Total power output : 1009W
Power Group 0:
================================================================================
Power Supply ------Input---- ------Output--- Status
Module Type Volts Amps Volts Amps
================================================================================
0/PM0 2kW-AC 0.0 0.0 0.0 0.0 FAILED or NO PWR
Total of Power Group 0: 0W/ 0.0A 0W/ 0.0A
Power Group 1:
================================================================================
Power Supply ------Input---- ------Output--- Status
Module Type Volts Amps Volts Amps
================================================================================
0/PM1 2kW-AC 228.8 4.7 12.1 83.4 OK
Total of Power Group 1: 1075W/ 4.7A 1009W/ 83.4A
================================================================================
Location Card Type Power Power Status
Allocated Used
Watts Watts
================================================================================
0/0 NCS1K4-1.2T-K9 260 - ON
0/1 NCS1K4-1.2T-K9 260 - ON
0/2 NCS1K4-1.2T-K9 260 - ON
0/3 NCS1K4-1.2T-K9 260 - ON
0/RP0 NCS1K4-CNTLR-K9 55 - ON
0/FT0 NCS1K4-FAN 100 - ON
0/FT1 NCS1K4-FAN 100 - ON
0/FT2 NCS1K4-FAN 100 - ON
0/SC0 NCS1004 35 - ON
The following example shows sample output from the show environment command with the voltages keyword.
sysadmin-vm:0_RP0# show environment voltages location 0/RP0
Wed Mar 20 04:43:04.524 UTC+00:00
================================================================================
Location VOLTAGE Value Crit Minor Minor Crit
Sensor (mV) (Lo) (Lo) (Hi) (Hi)
--------------------------------------------------------------------------------
0/RP0
ADM1266_VH1_12V 11982 10800 11040 12960 13200
ADM1266_VH3_3V3 3303 3036 3135 3465 3564
ADM1266_VH4_2V5 2493 2300 2375 2625 2700
ADM1266_VP1_1V8 1794 1656 1710 1890 1944
ADM1266_VP2_1V2 1189 1104 1140 1260 1296
ADM1266_3V3_STAND_BY 3303 3036 3135 3465 3564
ADM1266_VP4_3V3_CPU 3301 3036 3135 3465 3564
ADM1266_VP5_2V5_CPU 2490 2300 2375 2625 2700
ADM1266_VP6_1V8_CPU 1796 1656 1710 1890 1944
ADM1266_VP7_1V24_VCCREF 1233 1140 1178 1302 1339
ADM1266_VP8_1V05_CPU 1047 966 997 1102 1134
ADM1266_VP9_1V2_DDR_VDDQ 1200 1104 1140 1260 1296
ADM1266_VP10_1V0_VCCRAM 1056 500 650 1300 1400
ADM1266_VP11_VNN 876 400 550 1300 1400
ADM1266_VP12_VCCP 1062 300 450 1300 1400
ADM1266_VP13_0V6_VTT 600 552 570 630 648
ADM1293_DB_5V0 5014 4600 4750 5250 5400
ADM1293_DB_3V3 3317 3036 3135 3465 3564
ADM1293_DB_5V0_USB_0 5018 4000 4500 5500 6000
ADM1293_DB_5V0_USB_1 5036 4000 4500 5500 6000
ADM1293_MB_5V0_PMOD0 4932 4600 4750 5250 5400
ADM1293_MB_5V0_PMOD1 5012 4600 4750 5250 5400
ADM1293_MB_2V5_PLL 2485 2300 2375 2625 2700
To display the details of the muxponder slice, Field Programmable Devices (FPDs), and the card configuration in regen mode, use the show hw-module in XR EXEC or administration EXEC mode.
show hw-module { fpd | location location [ mxponder | mxponder-slice slicenumber | regen ] }
| fpd |
Displays the status of FPDs installed. |
| location location |
Specifies the location. |
|
mxponder |
Displays information for all the slices of the muxponder. |
|
mxponder-slice slicenumber |
Displays information for a specific slice of the muxponder. The valid values of slicenumber are 0 and 1. |
|
regen |
Displays information of card configuration in regen mode. |
None
XR EXEC
Administration EXEC
| Release | Modification |
|---|---|
|
Release 7.0.1 |
This command was introduced. |
|
Release 7.1.1 |
regen keyword was added. |
If the ISO image has new version of FPD, the Status column in show hw-module fpd command shows NEED UPGD. If the upgrade is required, use the upgrade hw-module location all fpd fpd_device_name command to start the upgrade. When the upgrade starts, the Status column in show hw-module fpd command sequentially shows UPGD PREP, UPGRADING, and the percentage of upgrade completion. After the upgrade is completed, the Status column shows RLOAD REQ if the ISO image requires reload; otherwise the Status column shows CURRENT.
![]() Note |
The upgrade of LC_OPT_MOD_FW FPD affects traffic. Hence, the user must perform this upgrade during a maintenance window. |
If reload is required:
If the FPGA location is 0/RP0, use the admin hw-module location 0/RP0 reload command. This command reboots only the CPU. Hence, the traffic is not impacted. If the FPGA location is 0/0, use the admin hw-module location all reload command. This command reboots NCS 1004. Hence, the traffic is impacted. After the reload is completed, the new FPGA runs the current version.
RP/0/RP0/CPU0:ios#show hw-module location 0/2 mxponder
Fri Mar 15 11:48:48.344 IST
Location: 0/2
Client Bitrate: 100GE
Trunk Bitrate: 500G
Status: Provisioned
LLDP Drop Enabled: FALSE
Client Port Mapper/Trunk Port CoherentDSP0/2/0/0 CoherentDSP0/2/0/1
Traffic Split Percentage
HundredGigECtrlr0/2/0/2 ODU40/2/0/0/1 100 0
HundredGigECtrlr0/2/0/3 ODU40/2/0/0/2 100 0
HundredGigECtrlr0/2/0/4 ODU40/2/0/0/3 100 0
HundredGigECtrlr0/2/0/5 ODU40/2/0/0/4 100 0
HundredGigECtrlr0/2/0/6 ODU40/2/0/0/5 100 0
HundredGigECtrlr0/2/0/7 ODU40/2/0/1/1 0 100
HundredGigECtrlr0/2/0/8 ODU40/2/0/1/2 0 100
HundredGigECtrlr0/2/0/9 ODU40/2/0/1/3 0 100
HundredGigECtrlr0/2/0/10 ODU40/2/0/1/4 0 100
HundredGigECtrlr0/2/0/11 ODU40/2/0/1/5 0 100
The following is a sample ouput of all the muxponder slice 0 configurations.
RP/0/RP0/CPU0:ios#show hw-module location 0/1 mxponder-slice 0
Fri Mar 15 06:04:18.348 UTC
Location: 0/1
Slice ID: 0
Client Bitrate: 100GE
Trunk Bitrate: 500G
Status: Provisioned
LLDP Drop Enabled: FALSE
Client Port Mapper/Trunk Port CoherentDSP0/1/0/0
Traffic Split Percentage
HundredGigECtrlr0/1/0/2 ODU40/1/0/0/1 100
HundredGigECtrlr0/1/0/3 ODU40/1/0/0/2 100
HundredGigECtrlr0/1/0/4 ODU40/1/0/0/3 100
HundredGigECtrlr0/1/0/5 ODU40/1/0/0/4 100
HundredGigECtrlr0/1/0/6 ODU40/1/0/0/5 100
The following is a sample ouput of all the muxponder slice 1 configurations.
RP/0/RP0/CPU0:ios#show hw-module location 0/1 mxponder-slice 1
Fri Mar 15 06:11:50.020 UTC
Location: 0/1
Slice ID: 1
Client Bitrate: 100GE
Trunk Bitrate: 400G
Status: Provisioned
LLDP Drop Enabled: TRUE
Client Port Mapper/Trunk Port CoherentDSP0/1/0/1
Traffic Split Percentage
HundredGigECtrlr0/1/0/8 ODU40/1/0/1/1 100
HundredGigECtrlr0/1/0/9 ODU40/1/0/1/2 100
HundredGigECtrlr0/1/0/10 ODU40/1/0/1/3 100
HundredGigECtrlr0/1/0/11 ODU40/1/0/1/4 100
The following is a sample ouput of card configuration in regen mode.
RP/0/RP0/CPU0:ios#show hw-module location 0/0 regen
Mon Mar 25 09:50:42.936 UTC
Location: 0/0
Trunk Bitrate: 400G
Status: Provisioned
East Port West Port
CoherentDSP0/0/0/0 CoherentDSP0/0/0/1
To retrieve and display the physical inventory information, use the show inventory command in XR EXEC or administration EXEC mode.
XR EXEC Mode
show inventory [ all | oid | raw | location location ]
Administration EXEC Mode
show inventory [ all | chassis | fan | power | raw | location location ]
| all |
(Optional) Displays inventory information for all the physical entities. |
| fan |
(Optional) Displays inventory information for the fans. |
| power |
(Optional) Displays inventory information for the power supply. |
| raw |
(Optional) Displays raw information about the chassis for diagnostic purposes. |
| chassis |
(Optional) Displays inventory information for the entire chassis. |
| location location |
(Optional) Displays inventory information for a specific node, or for all nodes in the chassis. |
| oid |
(Optional) Displays inventory information along with oid. |
All hardware inventory information is displayed.
XR EXEC
Administration EXEC
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command was introduced. |
Enter the show inventory command with the raw keyword to display every RFC 2737 entity installed in NCS 1004, including those without a PID, unique device identifier (UDI), or other physical identification. The raw keyword is primarily intended for troubleshooting problems with the show inventory command itself.
The following examples show sample output from the show inventory command in both EXEC and Administration EXEC modes.
sysadmin-vm:0_RP0# show inventory
Thu Mar 7 12:49:15.974 UTC+00:00
Name: Rack 0 Descr: Network Convergence System 1004 Chassis
PID: NCS1004 VID: V00 SN: CAT2217B020
Name: 0/0-Optics0/0/0/2 Descr: Cisco QSFP-100G-LR4-S Pluggable Optics Module
PID: QSFP-100G-LR4-S VID: V01 SN: FNS20530F3H
Name: 0/0-Optics0/0/0/3 Descr: Cisco 100G QSFP28 CWDM4 Pluggable Optics Module
PID: QSFP-100G-CWDM4-S VID: V02 SN: JFQ22108035
Name: 0/0-Optics0/0/0/4 Descr: Cisco 100G QSFP28 CWDM4 Pluggable Optics Module
PID: QSFP-100G-CWDM4-S VID: V02 SN: JFQ22108033
Name: 0/0-Optics0/0/0/5 Descr: Cisco 100G QSFP28 CWDM4 Pluggable Optics Module
PID: QSFP-100G-CWDM4-S VID: V02 SN: FNS22150QF8
Name: 0/0-Optics0/0/0/6 Descr: Cisco 100G QSFP28 CWDM4 Pluggable Optics Module
PID: QSFP-100G-CWDM4-S VID: V02 SN: FNS22150UJQ
Name: 0/0-Optics0/0/0/7 Descr: Cisco 100G QSFP28 CWDM4 Pluggable Optics Module
PID: QSFP-100G-CWDM4-S VID: V02 SN: FNS22150Q9P
Name: 0/0-Optics0/0/0/8 Descr: Cisco 100G QSFP28 CWDM4 Pluggable Optics Module
PID: QSFP-100G-CWDM4-S VID: V02 SN: FNS22150TE5
Name: 0/0-Optics0/0/0/9 Descr: Cisco 100G QSFP28 CWDM4 Pluggable Optics Module
PID: QSFP-100G-CWDM4-S VID: V02 SN: FNS22150TCP
Name: 0/0-Optics0/0/0/10 Descr: Cisco 100G QSFP28 CWDM4 Pluggable Optics Module
PID: QSFP-100G-CWDM4-S VID: V02 SN: FNS22150LDS
Name: 0/0-Optics0/0/0/11 Descr: Cisco 100G QSFP28 CWDM4 Pluggable Optics Module
PID: QSFP-100G-CWDM4-S VID: V02 SN: FNS22150L5H
Name: 0/0-Optics0/0/0/12 Descr: Cisco 100G QSFP28 CWDM4 Pluggable Optics Module
PID: QSFP-100G-CWDM4-S VID: V02 SN: FNS22150SED
Name: 0/0-Optics0/0/0/13 Descr: Cisco 100G QSFP28 CWDM4 Pluggable Optics Module
PID: QSFP-100G-CWDM4-S VID: V02 SN: FNS22150TUV
Name: 0/0 Descr: NCS1K4 12x QSFP28 2 Trunk C-Band DWDM card
PID: NCS1K4-1.2T-K9 VID: V00 SN: CAT2250B0A9
Name: 0/1-Optics0/1/0/2 Descr: Cisco 100G QSFP28 CWDM4 Pluggable Optics Module
PID: QSFP-100G-CWDM4-S VID: V02 SN: JFQ22108003
Name: 0/1-Optics0/1/0/3 Descr: Cisco 100G QSFP28 CWDM4 Pluggable Optics Module
PID: QSFP-100G-CWDM4-S VID: V02 SN: FNS22150QD8
Name: 0/1-Optics0/1/0/4 Descr: Cisco 100G QSFP28 CWDM4 Pluggable Optics Module
PID: QSFP-100G-CWDM4-S VID: V02 SN: JFQ22108004
Name: 0/1-Optics0/1/0/5 Descr: Cisco 100G QSFP28 SM-SR Pluggable Optics Module
PID: QSFP-100G-SM-SR VID: V02 SN: FNS22070GFW
Name: 0/1-Optics0/1/0/6 Descr: Cisco 100G QSFP28 SM-SR Pluggable Optics Module
PID: QSFP-100G-SM-SR VID: V01 SN: FNS20510ZFP
Name: 0/1-Optics0/1/0/7 Descr: Cisco 100G QSFP28 CWDM4 Pluggable Optics Module
PID: QSFP-100G-CWDM4-S VID: V02 SN: FNS22150QFJ
Name: 0/1-Optics0/1/0/8 Descr: Cisco 100G QSFP28 CWDM4 Pluggable Optics Module
PID: QSFP-100G-CWDM4-S VID: V02 SN: FNS22150TZF
Name: 0/1-Optics0/1/0/9 Descr: Cisco 100G QSFP28 CWDM4 Pluggable Optics Module
PID: QSFP-100G-CWDM4-S VID: V02 SN: FNS22150UJS
Name: 0/1-Optics0/1/0/10 Descr: Cisco 100G QSFP28 SM-SR Pluggable Optics Module
PID: QSFP-100G-SM-SR VID: V02 SN: FNS22070GCH
Name: 0/1-Optics0/1/0/11 Descr: Cisco 100G QSFP28 SM-SR Pluggable Optics Module
PID: QSFP-100G-SM-SR VID: V02 SN: FNS22070J79
Name: 0/1-Optics0/1/0/12 Descr: Cisco 100G QSFP28 SM-SR Pluggable Optics Module
PID: QSFP-100G-SM-SR VID: V02 SN: FNS22070GD7
Name: 0/1-Optics0/1/0/13 Descr: Cisco 100G QSFP28 CWDM4 Pluggable Optics Module
PID: QSFP-100G-CWDM4-S VID: V02 SN: FNS22150LHE
Name: 0/1 Descr: NCS1K4 12x QSFP28 2 Trunk C-Band DWDM card
PID: NCS1K4-1.2T-K9 VID: V00 SN: CAT2223B129
Name: 0/2-Optics0/2/0/2 Descr: Cisco 100G QSFP28 CWDM4 Pluggable Optics Module
PID: QSFP-100G-CWDM4-S VID: V02 SN: JFQ22108001
Name: 0/2-Optics0/2/0/3 Descr: Non-Cisco 100G QSFP28 CWDM4 Pluggable Optics Module
PID: LQ210CR-CPA1 VID: 01 SN: FG4657250006
Name: 0/2-Optics0/2/0/4 Descr: Cisco 100G QSFP28 CWDM4 Pluggable Optics Module
PID: QSFP-100G-CWDM4-S VID: V02 SN: JFQ2210802P
Name: 0/2-Optics0/2/0/5 Descr: Cisco 100G QSFP28 CWDM4 Pluggable Optics Module
PID: QSFP-100G-CWDM4-S VID: V02 SN: JFQ2210802Q
Name: 0/2-Optics0/2/0/6 Descr: Cisco 100G QSFP28 CWDM4 Pluggable Optics Module
PID: QSFP-100G-CWDM4-S VID: V02 SN: JFQ2210802R
Name: 0/2-Optics0/2/0/7 Descr: Cisco 100G QSFP28 CWDM4 Pluggable Optics Module
PID: QSFP-100G-CWDM4-S VID: V02 SN: JFQ2210802U
Name: 0/2-Optics0/2/0/8 Descr: Cisco 100G QSFP28 CWDM4 Pluggable Optics Module
PID: QSFP-100G-CWDM4-S VID: V02 SN: JFQ2146802T
Name: 0/2-Optics0/2/0/9 Descr: Cisco 100G QSFP28 CWDM4 Pluggable Optics Module
PID: QSFP-100G-CWDM4-S VID: V02 SN: JFQ2210800G
Name: 0/2-Optics0/2/0/10 Descr: Cisco 100G QSFP28 CWDM4 Pluggable Optics Module
PID: QSFP-100G-CWDM4-S VID: V02 SN: JFQ2210802M
Name: 0/2-Optics0/2/0/11 Descr: Cisco 100G QSFP28 CWDM4 Pluggable Optics Module
PID: QSFP-100G-CWDM4-S VID: V02 SN: JFQ2210800P
Name: 0/2 Descr: NCS1K4 12x QSFP28 2 Trunk C-Band DWDM card - Licensed
PID: NCS1K4-1.2T-L-K9 VID: V00 SN: CAT2250B09F
Name: 0/3-Optics0/3/0/2 Descr: Non-Cisco 100G QSFP28 LR4 Pluggable Optics Module
PID: ONS-QSFP28-LR4 VID: V01 SN: FNS20500RVT
Name: 0/3-Optics0/3/0/3 Descr: Cisco 100GE QSFP28 SR4 Pluggable Optics Module
PID: QSFP-100G-SR4-S VID: V03 SN: AVF2219S1D4
Name: 0/3-Optics0/3/0/4 Descr: Cisco 100GE QSFP28 SR4 Pluggable Optics Module
PID: QSFP-100G-SR4-S VID: V03 SN: AVF2219S16R
Name: 0/3-Optics0/3/0/5 Descr: Cisco 100GE QSFP28 SR4 Pluggable Optics Module
PID: QSFP-100G-SR4-S VID: V03 SN: AVF2219S16W
Name: 0/3-Optics0/3/0/6 Descr: Cisco 100GE QSFP28 SR4 Pluggable Optics Module
PID: QSFP-100G-SR4-S VID: V03 SN: AVF2219S17H
Name: 0/3-Optics0/3/0/7 Descr: Cisco 100GE QSFP28 SR4 Pluggable Optics Module
PID: QSFP-100G-SR4-S VID: V03 SN: AVF2219S1BA
Name: 0/3-Optics0/3/0/8 Descr: Cisco 100GE QSFP28 SR4 Pluggable Optics Module
PID: QSFP-100G-SR4-S VID: V03 SN: AVF2219S16G
Name: 0/3-Optics0/3/0/9 Descr: Cisco 100GE QSFP28 SR4 Pluggable Optics Module
PID: QSFP-100G-SR4-S VID: V03 SN: AVF2219S17N
Name: 0/3-Optics0/3/0/10 Descr: Cisco 100GE QSFP28 SR4 Pluggable Optics Module
PID: QSFP-100G-SR4-S VID: V03 SN: AVF2219S15W
Name: 0/3-Optics0/3/0/11 Descr: Cisco 100G QSFP28 CWDM4 Pluggable Optics Module
PID: QSFP-100G-CWDM4-S VID: V02 SN: FNS22150TES
Name: 0/3-Optics0/3/0/12 Descr: Cisco 100GE QSFP28 SR4 Pluggable Optics Module
PID: QSFP-100G-SR4-S VID: V03 SN: AVF2219S16S
Name: 0/3-Optics0/3/0/13 Descr: Cisco 100GE QSFP28 SR4 Pluggable Optics Module
PID: QSFP-100G-SR4-S VID: V03 SN: AVF2219S178
Name: 0/3 Descr: NCS1K4 12x QSFP28 2 Trunk C-Band DWDM card
PID: NCS1K4-1.2T-K9 VID: V00 SN: CAT2236B01A
Name: 0/RP0 Descr: Network Convergence System 1004 Controller
PID: NCS1K4-CNTLR-K9 VID: V00 SN: CAT2217B09N
Name: 0/FT0 Descr: Network Convergence System 1004 Fan
PID: NCS1K4-FAN VID: V00 SN: CAT2218B12J
Name: 0/FT1 Descr: Network Convergence System 1004 Fan
PID: NCS1K4-FAN VID: V00 SN: CAT2218B125
Name: 0/FT2 Descr: Network Convergence System 1004 Fan
PID: NCS1K4-FAN VID: V00 SN: CAT2218B124
Name: 0/PM0 Descr: Network Convergence System 1004 AC Power Supply Unit
PID: NCS1K4-AC-PSU VID: V00 SN: POG2212CL12
Name: 0/PM1 Descr: Network Convergence System 1004 AC Power Supply Unit
PID: NCS1K4-AC-PSU VID: V00 SN: POG2212CL2Q
Name: 0/SC0 Descr: Network Convergence System 1004 Chassis
PID: NCS1004 VID: V00 SN: CAT2217B020
RP/0/RP0/CPU0:ios# show inventory
Thu Mar 7 10:39:50.321 UTC
NAME: "0/0", DESCR: "NCS1K4 12x QSFP28 2 Trunk C-Band DWDM card"
PID: NCS1K4-1.2T-K9 , VID: V00, SN: CAT2250B0A9
NAME: "0/0-Optics0/0/0/2", DESCR: "Cisco QSFP-100G-LR4-S Pluggable Optics Module"
PID: QSFP-100G-LR4-S , VID: V01 , SN: FNS20530F3H
NAME: "0/0-Optics0/0/0/3", DESCR: "Cisco 100G QSFP28 CWDM4 Pluggable Optics Module"
PID: QSFP-100G-CWDM4-S , VID: V02 , SN: JFQ22108035
NAME: "0/0-Optics0/0/0/4", DESCR: "Cisco 100G QSFP28 CWDM4 Pluggable Optics Module"
PID: QSFP-100G-CWDM4-S , VID: V02 , SN: JFQ22108033
NAME: "0/0-Optics0/0/0/5", DESCR: "Cisco 100G QSFP28 CWDM4 Pluggable Optics Module"
PID: QSFP-100G-CWDM4-S , VID: V02 , SN: FNS22150QF8
NAME: "0/0-Optics0/0/0/6", DESCR: "Cisco 100G QSFP28 CWDM4 Pluggable Optics Module"
PID: QSFP-100G-CWDM4-S , VID: V02 , SN: FNS22150UJQ
NAME: "0/0-Optics0/0/0/7", DESCR: "Cisco 100G QSFP28 CWDM4 Pluggable Optics Module"
PID: QSFP-100G-CWDM4-S , VID: V02 , SN: FNS22150Q9P
NAME: "0/0-Optics0/0/0/8", DESCR: "Cisco 100G QSFP28 CWDM4 Pluggable Optics Module"
PID: QSFP-100G-CWDM4-S , VID: V02 , SN: FNS22150TE5
NAME: "0/0-Optics0/0/0/9", DESCR: "Cisco 100G QSFP28 CWDM4 Pluggable Optics Module"
PID: QSFP-100G-CWDM4-S , VID: V02 , SN: FNS22150TCP
NAME: "0/0-Optics0/0/0/10", DESCR: "Cisco 100G QSFP28 CWDM4 Pluggable Optics Module"
PID: QSFP-100G-CWDM4-S , VID: V02 , SN: FNS22150LDS
NAME: "0/0-Optics0/0/0/11", DESCR: "Cisco 100G QSFP28 CWDM4 Pluggable Optics Module"
PID: QSFP-100G-CWDM4-S , VID: V02 , SN: FNS22150L5H
NAME: "0/0-Optics0/0/0/12", DESCR: "Cisco 100G QSFP28 CWDM4 Pluggable Optics Module"
PID: QSFP-100G-CWDM4-S , VID: V02 , SN: FNS22150SED
NAME: "0/0-Optics0/0/0/13", DESCR: "Cisco 100G QSFP28 CWDM4 Pluggable Optics Module"
PID: QSFP-100G-CWDM4-S , VID: V02 , SN: FNS22150TUV
NAME: "0/1", DESCR: "NCS1K4 12x QSFP28 2 Trunk C-Band DWDM card"
PID: NCS1K4-1.2T-K9 , VID: V00, SN: CAT2223B129
NAME: "0/1-Optics0/1/0/2", DESCR: "Cisco 100G QSFP28 CWDM4 Pluggable Optics Module"
PID: QSFP-100G-CWDM4-S , VID: V02 , SN: JFQ22108003
NAME: "0/1-Optics0/1/0/3", DESCR: "Cisco 100G QSFP28 CWDM4 Pluggable Optics Module"
PID: QSFP-100G-CWDM4-S , VID: V02 , SN: FNS22150QD8
NAME: "0/1-Optics0/1/0/4", DESCR: "Cisco 100G QSFP28 CWDM4 Pluggable Optics Module"
PID: QSFP-100G-CWDM4-S , VID: V02 , SN: JFQ22108004
NAME: "0/1-Optics0/1/0/5", DESCR: "Cisco 100G QSFP28 SM-SR Pluggable Optics Module"
PID: QSFP-100G-SM-SR , VID: V02 , SN: FNS22070GFW
NAME: "0/1-Optics0/1/0/6", DESCR: "Cisco 100G QSFP28 SM-SR Pluggable Optics Module"
PID: QSFP-100G-SM-SR , VID: V01 , SN: FNS20510ZFP
NAME: "0/1-Optics0/1/0/7", DESCR: "Cisco 100G QSFP28 CWDM4 Pluggable Optics Module"
PID: QSFP-100G-CWDM4-S , VID: V02 , SN: FNS22150QFJ
NAME: "0/1-Optics0/1/0/8", DESCR: "Cisco 100G QSFP28 CWDM4 Pluggable Optics Module"
PID: QSFP-100G-CWDM4-S , VID: V02 , SN: FNS22150TZF
NAME: "0/1-Optics0/1/0/9", DESCR: "Cisco 100G QSFP28 CWDM4 Pluggable Optics Module"
PID: QSFP-100G-CWDM4-S , VID: V02 , SN: FNS22150UJS
NAME: "0/1-Optics0/1/0/10", DESCR: "Cisco 100G QSFP28 SM-SR Pluggable Optics Module"
PID: QSFP-100G-SM-SR , VID: V02 , SN: FNS22070GCH
NAME: "0/1-Optics0/1/0/11", DESCR: "Cisco 100G QSFP28 SM-SR Pluggable Optics Module"
PID: QSFP-100G-SM-SR , VID: V02 , SN: FNS22070J79
NAME: "0/1-Optics0/1/0/12", DESCR: "Cisco 100G QSFP28 SM-SR Pluggable Optics Module"
PID: QSFP-100G-SM-SR , VID: V02 , SN: FNS22070GD7
NAME: "0/1-Optics0/1/0/13", DESCR: "Cisco 100G QSFP28 CWDM4 Pluggable Optics Module"
PID: QSFP-100G-CWDM4-S , VID: V02 , SN: FNS22150LHE
NAME: "0/2", DESCR: "NCS1K4 12x QSFP28 2 Trunk C-Band DWDM card - Licensed"
PID: NCS1K4-1.2T-L-K9 , VID: V00, SN: CAT2250B09F
NAME: "0/2-Optics0/2/0/2", DESCR: "Cisco 100G QSFP28 CWDM4 Pluggable Optics Module"
PID: QSFP-100G-CWDM4-S , VID: V02 , SN: JFQ22108001
NAME: "0/2-Optics0/2/0/3", DESCR: "Non-Cisco 100G QSFP28 CWDM4 Pluggable Optics Module"
PID: LQ210CR-CPA1 , VID: 01 , SN: FG4657250006
NAME: "0/2-Optics0/2/0/4", DESCR: "Cisco 100G QSFP28 CWDM4 Pluggable Optics Module"
PID: QSFP-100G-CWDM4-S , VID: V02 , SN: JFQ2210802P
NAME: "0/2-Optics0/2/0/5", DESCR: "Cisco 100G QSFP28 CWDM4 Pluggable Optics Module"
PID: QSFP-100G-CWDM4-S , VID: V02 , SN: JFQ2210802Q
NAME: "0/2-Optics0/2/0/6", DESCR: "Cisco 100G QSFP28 CWDM4 Pluggable Optics Module"
PID: QSFP-100G-CWDM4-S , VID: V02 , SN: JFQ2210802R
NAME: "0/2-Optics0/2/0/7", DESCR: "Cisco 100G QSFP28 CWDM4 Pluggable Optics Module"
PID: QSFP-100G-CWDM4-S , VID: V02 , SN: JFQ2210802U
NAME: "0/2-Optics0/2/0/8", DESCR: "Cisco 100G QSFP28 CWDM4 Pluggable Optics Module"
PID: QSFP-100G-CWDM4-S , VID: V02 , SN: JFQ2146802T
NAME: "0/2-Optics0/2/0/9", DESCR: "Cisco 100G QSFP28 CWDM4 Pluggable Optics Module"
PID: QSFP-100G-CWDM4-S , VID: V02 , SN: JFQ2210800G
NAME: "0/2-Optics0/2/0/10", DESCR: "Cisco 100G QSFP28 CWDM4 Pluggable Optics Module"
PID: QSFP-100G-CWDM4-S , VID: V02 , SN: JFQ2210802M
NAME: "0/2-Optics0/2/0/11", DESCR: "Cisco 100G QSFP28 CWDM4 Pluggable Optics Module"
PID: QSFP-100G-CWDM4-S , VID: V02 , SN: JFQ2210800P
NAME: "0/3", DESCR: "NCS1K4 12x QSFP28 2 Trunk C-Band DWDM card"
PID: NCS1K4-1.2T-K9 , VID: V00, SN: CAT2236B01A
NAME: "0/3-Optics0/3/0/2", DESCR: "Non-Cisco 100G QSFP28 LR4 Pluggable Optics Module"
PID: ONS-QSFP28-LR4 , VID: V01 , SN: FNS20500RVT
NAME: "0/3-Optics0/3/0/3", DESCR: "Cisco 100GE QSFP28 SR4 Pluggable Optics Module"
PID: QSFP-100G-SR4-S , VID: V03 , SN: AVF2219S1D4
NAME: "0/3-Optics0/3/0/4", DESCR: "Cisco 100GE QSFP28 SR4 Pluggable Optics Module"
PID: QSFP-100G-SR4-S , VID: V03 , SN: AVF2219S16R
NAME: "0/3-Optics0/3/0/5", DESCR: "Cisco 100GE QSFP28 SR4 Pluggable Optics Module"
PID: QSFP-100G-SR4-S , VID: V03 , SN: AVF2219S16W
NAME: "0/3-Optics0/3/0/6", DESCR: "Cisco 100GE QSFP28 SR4 Pluggable Optics Module"
PID: QSFP-100G-SR4-S , VID: V03 , SN: AVF2219S17H
NAME: "0/3-Optics0/3/0/7", DESCR: "Cisco 100GE QSFP28 SR4 Pluggable Optics Module"
PID: QSFP-100G-SR4-S , VID: V03 , SN: AVF2219S1BA
NAME: "0/3-Optics0/3/0/8", DESCR: "Cisco 100GE QSFP28 SR4 Pluggable Optics Module"
PID: QSFP-100G-SR4-S , VID: V03 , SN: AVF2219S16G
NAME: "0/3-Optics0/3/0/9", DESCR: "Cisco 100GE QSFP28 SR4 Pluggable Optics Module"
PID: QSFP-100G-SR4-S , VID: V03 , SN: AVF2219S17N
NAME: "0/3-Optics0/3/0/10", DESCR: "Cisco 100GE QSFP28 SR4 Pluggable Optics Module"
PID: QSFP-100G-SR4-S , VID: V03 , SN: AVF2219S15W
NAME: "0/3-Optics0/3/0/11", DESCR: "Cisco 100G QSFP28 CWDM4 Pluggable Optics Module"
PID: QSFP-100G-CWDM4-S , VID: V02 , SN: FNS22150TES
NAME: "0/3-Optics0/3/0/12", DESCR: "Cisco 100GE QSFP28 SR4 Pluggable Optics Module"
PID: QSFP-100G-SR4-S , VID: V03 , SN: AVF2219S16S
NAME: "0/3-Optics0/3/0/13", DESCR: "Cisco 100GE QSFP28 SR4 Pluggable Optics Module"
PID: QSFP-100G-SR4-S , VID: V03 , SN: AVF2219S178
NAME: "0/RP0", DESCR: "Network Convergence System 1004 Controller"
PID: NCS1K4-CNTLR-K9 , VID: V00, SN: CAT2217B09N
NAME: "0/SC0", DESCR: "Network Convergence System 1004 Chassis"
PID: NCS1004 , VID: V00, SN: CAT2217B020
NAME: "Rack 0", DESCR: "Network Convergence System 1004 Chassis"
PID: NCS1004 , VID: V00, SN: CAT2217B020
NAME: "0/FT0", DESCR: "Network Convergence System 1004 Fan"
PID: NCS1K4-FAN , VID: V00, SN: CAT2218B12J
NAME: "0/FT1", DESCR: "Network Convergence System 1004 Fan"
PID: NCS1K4-FAN , VID: V00, SN: CAT2218B125
NAME: "0/FT2", DESCR: "Network Convergence System 1004 Fan"
PID: NCS1K4-FAN , VID: V00, SN: CAT2218B124
NAME: "0/PM0", DESCR: "Network Convergence System 1004 AC Power Supply Unit "
PID: NCS1K4-AC-PSU , VID: V00, SN: POG2212CL12
NAME: "0/PM1", DESCR: "Network Convergence System 1004 AC Power Supply Unit "
PID: NCS1K4-AC-PSU , VID: V00, SN: POG2212CL2Q
To display the status of various LEDs present in NCS 1004, use the show led command in administration EXEC mode.
show led [ location location ]
| location location |
(Optional) Displays LED information for a specific location. |
The status of all the LEDs present in NCS 1004 is displayed.
Administration EXEC
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command was introduced. |
Enter the show LED command in administration EXEC mode to display the status of all the LEDs present in NCS 1004.
The following example shows sample output from the show led command.
sysadmin-vm:0_RP0# show led
Wed Mar 20 04:45:25.457 UTC+00:00
=============================================================
Location LED Name Mode Color
=============================================================
0/0
0/0-Status LED WORKING GREEN
0/1
0/1-Status LED WORKING GREEN
0/2
0/2-Status LED WORKING GREEN
0/3
0/3-Status LED WORKING GREEN
0/RP0
0/RP0-Attention LED WORKING OFF
0/RP0-SYS LED WORKING AMBER
0/RP0-PSU LED WORKING RED
0/RP0-FAN LED WORKING GREEN
0/FT0
0/FT0-Status LED WORKING GREEN
0/FT1
0/FT1-Status LED WORKING GREEN
0/FT2
0/FT2-Status LED WORKING GREEN
0/PM0
0/PM0-Status LED WORKING AMBER
0/PM1
0/PM1-Status LED WORKING GREEN
To display information and status for each node in the system, use the show platform command in XR EXEC or administration EXEC mode.
Administration EXEC Mode
show platform [{ detail | location | slices} location]
XR EXEC Mode
show platform [ vm | 0/RP0 ]
| detail |
(Optional) Displays the details of node type and state. |
| location |
(Optional) Displays the location of node. |
| slices |
(Optional) Displays the summary information of each slice in the node. |
| location |
(Optional) Node location such as 0/FT0, 0/RP0. |
| vm |
(Optional) Displays the virtual machine information of node. |
The status and information are displayed for all the nodes in the system.
XR EXEC
Administration EXEC
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command was introduced. |
Enter the show platform command in administration EXEC mode to display the output for the entire system.
The following example shows sample output from the show platform command.
sysadmin-vm:0_RP0# show platform
Wed Mar 20 04:27:21.562 UTC+00:00
Location Card Type HW State SW State Config State
----------------------------------------------------------------------------
0/0 NCS1K4-1.2T-K9 OPERATIONAL N/A NSHUT
0/1 NCS1K4-1.2T-K9 OPERATIONAL N/A NSHUT
0/2 NCS1K4-1.2T-K9 OPERATIONAL N/A NSHUT
0/3 NCS1K4-1.2T-K9 OPERATIONAL N/A NSHUT
0/RP0 NCS1K4-CNTLR-K9 OPERATIONAL OPERATIONAL NSHUT
0/FT0 NCS1K4-FAN OPERATIONAL N/A NSHUT
0/FT1 NCS1K4-FAN OPERATIONAL N/A NSHUT
0/FT2 NCS1K4-FAN OPERATIONAL N/A NSHUT
0/PM0 NCS1K4-AC-PSU OPERATIONAL N/A NSHUT
0/PM1 NCS1K4-AC-PSU OPERATIONAL N/A NSHUT
0/SC0 NCS1004 OPERATIONAL N/A NSHUT
The following example shows sample output from the show platform detail command.
sysadmin-vm:0_RP0# show platform detail
Wed Mar 20 04:31:02.480 UTC+00:00
MODULE HW OPER SW OPER
LOCATION : PID : DESCRIPTION : VID/SN : STATE : STATE : CONFIGURATION : HW VERSION : LAST EVENT : LAST EVENT REASON :
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
0/0 NCS1K4-1.2T-K9 NCS1K4 12x QSFP28 2 Trunk C-Band DWDM card V00 OPERATIONAL N/A NSHUT RST 0.1 HW_EVENT_OK HW READY
0/1 NCS1K4-1.2T-K9 NCS1K4 12x QSFP28 2 Trunk C-Band DWDM card V00 OPERATIONAL N/A NSHUT RST 0.1 HW_EVENT_OK HW READY
0/2 NCS1K4-1.2T-K9 NCS1K4 12x QSFP28 2 Trunk C-Band DWDM card V00 OPERATIONAL N/A NSHUT RST 0.1 HW_EVENT_OK HW READY
0/3 NCS1K4-1.2T-K9 NCS1K4 12x QSFP28 2 Trunk C-Band DWDM card V00 OPERATIONAL N/A NSHUT RST 0.1 HW_EVENT_OK HW READY
0/RP0 NCS1K4-CNTLR-K9 Network Convergence System 1004 Controller V00 OPERATIONAL OPERATIONAL NSHUT RST 0.1 HW_EVENT_OK HW Event OK
0/FT0 NCS1K4-FAN Network Convergence System 1004 Fan V00 OPERATIONAL N/A NSHUT RST 0.1 HW_EVENT_OK HW Operational
0/FT1 NCS1K4-FAN Network Convergence System 1004 Fan V00 OPERATIONAL N/A NSHUT RST 0.1 HW_EVENT_OK HW Operational
0/FT2 NCS1K4-FAN Network Convergence System 1004 Fan V00 OPERATIONAL N/A NSHUT RST 0.1 HW_EVENT_OK HW Operational
0/PM0 NCS1K4-AC-PSU Network Convergence System 1004 AC Power Supply Unit V00 OPERATIONAL N/A NSHUT RST 0.0 HW_EVENT_OK HW Operational
0/PM1 NCS1K4-AC-PSU Network Convergence System 1004 AC Power Supply Unit V00 OPERATIONAL N/A NSHUT RST 0.0 HW_EVENT_OK HW Operational
0/SC0 NCS1004 Network Convergence System 1004 Chassis V00 OPERATIONAL N/A NSHUT RST 0.1 HW_EVENT_OK HW Event OK
RP/0/RP0/CPU0:ios# show platform
Wed Mar 20 04:23:12.582 UTC
Node Type State Config state
--------------------------------------------------------------------------------
0/0 NCS1K4-1.2T-K9 OPERATIONAL NSHUT
0/1 NCS1K4-1.2T-K9 OPERATIONAL NSHUT
0/2 NCS1K4-1.2T-K9 OPERATIONAL NSHUT
0/3 NCS1K4-1.2T-K9 OPERATIONAL NSHUT
0/RP0/CPU0 NCS1K4-CNTLR-K9(Active) IOS XR RUN NSHUT
0/FT0 NCS1K4-FAN OPERATIONAL NSHUT
0/FT1 NCS1K4-FAN OPERATIONAL NSHUT
0/FT2 NCS1K4-FAN OPERATIONAL NSHUT
0/PM0 NCS1K4-AC-PSU OPERATIONAL NSHUT
0/PM1 NCS1K4-AC-PSU OPERATIONAL NSHUT
0/SC0 NCS1004 OPERATIONAL NSHUT
To specify the out-of-band refresh interval for RSVP, use the signalling refresh out-of-band interval command in RSVP controller configuration mode.
signalling refresh out-of-band interval interval
| interval |
Specifies the refresh interval (180-86400 seconds). |
45 seconds
RSVP controller configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
This command applies only to the RSVP sessions associated with GMPLS UNI tunnels.
The following example shows how to specify 200 seconds for the out-of-band interface refresh interval.
RP/0/RP0/CPU0:ios(config)#rsvp
RP/0/RP0/CPU0:ios(config-rsvp)#controller Optics0/0/0/0
RP/0/RP0/CPU0:ios(config-rsvp-ctrl)#signalling refresh out-of-band interval 200
RP/0/RP0/CPU0:ios(config-rsvp-ctrl)#
To specify the number of missed refresh messages allowed before states are deleted for optical tunnels, use the signalling refresh out-of-band missed command in RSVP controller configuration mode.
signalling refresh out-of-band missed mis-count
| mis-count |
Number of missed refresh messages allowed before states are deleted for optical tunnels (1-48). |
The default value is 12.
RSVP controller configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
This command applies only to the RSVP sessions associated with GMPLS UNI tunnels.
The following example shows how to specify a maximum of 10 messages for the number of allowed missed refresh messages.
RP/0/RP0/CPU0:ios(config)#rsvp
RP/0/RP0/CPU0:ios(config-rsvp)#controller Optics0/0/0/0
RP/0/RP0/CPU0:ios(config-rsvp-ctrl)#signalling refresh out-of-band missed 10
RP/0/RP0/CPU0:ios(config-rsvp-ctrl)#
To specify the ID of the GMPLS UNI tunnel, use the tunnel-id command in GMPLS UNI controller tunnel-properties configuration sub-mode.
tunnel-id number
| number |
Specifies the tunnel ID. |
None
GMPLS UNI controller tunnel-properties configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
The following example shows how to specify a tunnel ID.
RP/0/RP0/CPU0:ios(config)#mpls traffic-eng
RP/0/RP0/CPU0:ios(config-mpls-te)#gmpls optical-uni
RP/0/RP0/CPU0:ios(config-te-gmpls)#controller Optics0/0/0/0
RP/0/RP0/CPU0:ios(config-te-gmpls-cntl)#tunnel-properties
RP/0/RP0/CPU0:ios(config-te-gmpls-tun)#tunnel-id 5
RP/0/RP0/CPU0:ios(config-te-gmpls-tun)#
To configure tunnel-specific information for a GMPLS UNI controller, use the tunnel-properties command in GMPLS-UNI configuration sub-mode.
tunnel-properties
| This command has no keywords or arguments. |
None
GMPLS UNI configuration
| Release | Modification |
|---|---|
| Release 7.0.1 |
This command is introduced. |
The following example shows how to enter the sub-mode to configure tunnel-specific information for a GMPLS UNI controller.
RP/0/RP0/CPU0:ios(config)#mpls traffic-eng
RP/0/RP0/CPU0:ios(config-mpls-te)#gmpls optical-uni
RP/0/RP0/CPU0:ios(config-te-gmpls)#controller Optics0/0/0/0
RP/0/RP0/CPU0:ios(config-te-gmpls-cntl)#tunnel-properties
RP/0/RP0/CPU0:ios(config-te-gmpls-tun)#