I got response from Cisco Tech support and there are a few things not correctly described in the manual.
First, ASR router supports key size 1024 bit or smaller contrary to its manual(supporting up to 2048 bit key).
Second, only the key part of SSH public key must be 'de'coded w/ base64 en/decoding program.
SSH Key Generation
ssh-keygen -b 1024 -t rsa -f ...
You must commit replace with an empty config file. This will wipe the config out completely. Also keep in mind the admin context. You'll need to go into the admin context and commit replace that config as well if you want to reset the settings inside the admin context.
Have you tried walking the MIB/OIDs in question from a management station? After having spent a lot of time w/firmware QA, I've noticed things like show commands are likely to not display correct info, even when the OIDs are poll-able. I recommend using and knowing Net-SNMP tools and utils as debug before trying to poll the information in cacti, observium, ...
To factory reset the ASR, I found the way here
We only need to apply this command
commit replace best-effort
As we don't have any configuration file target, actual configuration will be substitute with an empty file
On ASR9k running IOS-XR ICMP packets destined to the router are handled by LTPS (Local Packet Transport System). I believe that under normal circumstances the entire processing of such packet is done on ingress linecard CPU.
Once the NP on ingress LC detects the packet is for-us, it hands it over to LTPS. LTPS will perform policing, conforming packets are ...
In IOS-XR, there are different concepts of authorization than in classic IOS. In classic IOS, there's only command authorization, which allows or denies specific commands, typically sent to a tacacs+ or radius server. In IOS-XR, there is command authorization (aaa authorization commands) (but you're better off doing this via task-groups) and exec ...
The mib 18.104.22.168.22.214.171.124.91 works on ASR1001s at least.
Running the following from my monitoring box:
snmpwalk -v2c -c <community-string> <asr1001-name> 126.96.36.199.188.8.131.52.91
Gives an output of:
CISCO-ENTITY-SENSOR-MIB::entSensorType.4 = INTEGER: amperes(5)
CISCO-ENTITY-SENSOR-MIB::entSensorType.5 = INTEGER: voltsAC(3)
Class-maps can be used for much more than just policing traffic.
The more general "cbQOSClassMapStats" would show a different count if you were also taking other actions than just "police".
For example, if in the same class map you were also queueing, you'd need to look at the "cbQOSQueueingStats" OID.
I'd recommend reading through Cisco's MIB object ...
Unfortunately on IOS the show advertised command has always showed the attributes of the route pre policy. It will drop routes that were denied but the attributes are the original ones. Instead I recommend setting up a bgp session to another one of your devices, turning on soft reconfig inbound and denying all routes. This will let you look at the attributes ...
As a workaround, I configured Lo0 interface as a passive and advertised only passive interfaces into ISIS:
RP/0/RP0/CPU0:PE2#sh run router isis lab
Mon Apr 19 11:01:50.732 UTC
router isis lab
address-family ipv4 unicast
address-family ipv4 ...
The issue here is the community string needs to be set by the sender, not the route policy. The route policy sets the community at the end of the processing, so the if test never sees the community string and sets local pref to 95. The result is local pref 95 and community 65535:0 being added.
Here are my answers:
No, remote-as value (of neighbor 184.108.40.206) stays unchanged of 65200.
Yes, even you do not have 'address-family ipv4 unicast'.
Yes, the neighbor inherits policies under 'address-family l2vpn vpls-vpws'.
You can verify all the answers by using commands:
#show bgp neighbors 220.127.116.11 configuration
To wipe existing config, and start from default configuration where you will be asked to set initial username and password for console connection you need just few commands:
After this command just reload the device. This works very well for me on ASR9010
I believe this is not possible as @jwbensley said. Though it's also unlikely that cisco.com explicitly says that this functionality isn't implemented.
When you're viewing attributes such as community you're looking at BGP table. Route is getting into BGP table after policy has been applied. So if you change attributes with policy, you can only see modified ...
Not Bash or Python necessarily, but EEM (Embedded Event Manager) is meant for this purpose. You use it to do various things (such as run scripts) based on certain criteria (such as when a specific log message is seen or at a certain time/date). You can either define actions in a sequence for it to run, or you can have it execute a script stored on the ...
Sorry I don't have a system actually in front of me to get you actual output, but look for "show qos interface ..." and that should have the configured hardware values for all the QoS parameters.
The CLI is going to be something like:
show qos interface gigE 0/0/0/0.101 ingress
(it might actually be "input" or "output" instead of "ingress" or "egress" ...
CISCO-IETF-PW-MIB::cpwVcTable provides pseudo-wire VC status and some other configuration data.
CISCO-IETF-PW-MIB::cpwVcPerfTotalTable gives per-VC packets and bytes 64-bit counters.
With net-snmp utils you can try queries like (works on ASR9K):
snmptable -v2c -c public -M /usr/share/snmp/CISCO -m CISCO-IETF-PW-MIB -IR -Ci YOUR_ROUTER_NAME_OR_IP cpwVcTable
The first command sets the AD for all routes learned by OSPF. This is basically the traditional AD command, as seen in IOS since they invented dirt.
The second allows you to set different AD's for different types of OSPF routes - so different values for externals vs inter-area vs intra-area. I suppose the idea here is to be able to prefer, say, a route ...
So My question is, how do I find that product ID "SASR1K1XU-313S" if possible in my current routers CLI.
You likely won't. This is simply a software license component that is only one part of what you need.
To illustrate, here is one of a number of examples of the type of "parts list" you will generate when ordering such a router from Cisco's ASR 1000 ...
You can use below commands,
show tech info
show tech info will take long time to load because it will show all technical specifications and many other details as well.
You don't need to think about router if you are going to receive encryption traffic. But if you want to generate traffic with additional security you need to ...
I have found an answer for this question:
> I would like to know how I must interpret the "show tcp detail pcb" and specifically the following line (IOS XR device):
> Datagrams (in bytes): MSS 1460, peer MSS 1460, min MSS 1946, max MSS 1946
> Is the IOS XR device using MSS 1460 or MSS 1946.
Its using 1460.
Try "show bgp ipv4 unicast A.B.C.D/length detail"
You will see a "received-only" path. This is the path you are receiving, including received communities, before any policies are applied.
If soft reconfiguration inbound is configured, ...