‘学习笔记’ 分类存档

Install and deploy Cisco WAE 7.1.1


I installed the WAE 6.4.5 at formal and summaried to Blog, e.g: INSTALL CISCO WAE 6.4.5. After 7.0, install/config have big change and similar with NSO that easy/module to deploy. For this article, only talk about how to install and enable.

Auto source profile

Similar with NSO, add “source” command to “.bash_profile” that in MacOS. That will let you direct to login to WAE but not do “source wae711/waerc”, as follow:

[root@frank ~]# echo "source /opt/wae711/waerc" >> .bash_profile
[root@frank ~]# more .bash_profile | grep wae
source /opt/wae711/waerc



MacOS Tips


System Preferences -> Accessibility -> Mouse & Trackpad -> Trackpad Options -> Enable dragging -> three finger drag


默认分辨率是1680×1050, 看着不舒服,改成1440×900就可以了
System Preferences -> Displays -> Scaled ->


System Preferences -> Desktop & Screen Saver -> Hot corners -> choose one corner and choose “Start Screen Saver”


  • 在fusion的setting中启动Retina 显示,并开启自动调整
  • 在win10中安装Vmware tools
  • 在win10的Display中,选择高级scaling setting,打开“let windows try to fix apps ……”








CISCO WAE: wae-db dead but pid file exists


If you found similar alarms, you can follow the guide and try to workaround the issue.


My customer found WAE REST API not workable, after checked, found wae-db have issue and report alarm, as follow.
And try to restart the WAE service and reload VM, not any useful.

[root@wae-auto wae-db]# service --status-all | grep wae
JAVA_EXECUTABLE or HSQLDB_JAR_PATH in '/etc/sysconfig/hsqldb' is set to a non-file.
wae-appenginecore is running OK, with PID=18606
wae-core is running OK, with PID=18163
wae-db dead but pid file exists  <<<<<<
wae-designapiserver is running OK, with PID=18847
wae-messaging is running OK, with PID=17874
wae-ni is running OK, with PID=17525
wae-osc is running OK, with PID=18369
wae-svcs-dashui is running OK, with PID=16652
wae-svcs-db is running OK, with PID=16277
wae-svcs-localrepo is not running
wae-svcs-log is running OK, with PID=16497
wae-svcs-logagent is running OK, with PID=16570
wae-svcs-metricsbkr is running OK, with PID=16716
wae-svcs-metricsd is running OK, with PID=16806
wae-svcs-mon is running OK, with PID=16138
wae-svcs-ui is running OK, with PID=16917
wae-system-server is running OK, with PID=16186
wae-web-server is running OK, with PID=17761



ASR9k Netflow and QOS order in the inbound direction

My customer match a issue that business traffics take IP6,7 flag, then the traffics auto mapping to EXP6,7 that cause control police congestion, and ISIS flapping due to BFD flap. So they want to check which traffics have incorrect flag by netflow, so need to check ording for netflow and QOS at input direction. I check some documents, nobody notice that, so the article will show test info, you can check if you need. Finaly test result: At ingress direction, packets will be cached first by netflow, then do other action in QOS.

Btw, due to auto mapping from TOS to EXP by range, e.g: TOS 192-223 will map to EXP6; TOS 223-255 will map to EXP7. So if we want to check the issue by netflow, suggest filter EXP data, as in my follow test, check by follow command:

RP/0/RSP1/CPU0:ASR9006-G#sh flow monitor test-mpls cache brief location 0/0/cpu0 | i 7-0
Fri Jan  8 04:57:39.604 UTC
      LDP        30000-7-0        40034-7-1           -                -                -                -          Te0/0/0/2       Te0/0/0/1       Fwd                  3888         36           Egr      0xff     icmp     0          2048