9月 29th, 2019
Awesome upgrade cmd for eXR, that will help customer simplify upgrade procedure and do upgrade automation! Feature release from 652. Just tested and summarized.
I summarized normal upgrade eXR version by install add/prepare/active at former: Upgrade/Install Packages in eXR. For the article, will summary how to upgrade by install replaced.
“Install replaced” is a new cmd that help customer upgrade only by one cmd, don’t need to add/prepare/active steps, that only support by GISO. What is GISO? That is an image bundle, customer can flexibly customize the image, e.g only bundle: ISIS rpm + mini iso + k9 rpm + configuration to one GISO, more GISO information, please check CCO Doc: Flexible Packaging Configuration Guide for Cisco NCS 5500 Series Routers
PS: “Install replaced” that will not affect running configuration, and auto removes inactive rpm, and commit.
Build GISO
完整阅读
7月 17th, 2019
Seperate RPM Pacakage
Check now version
Due to now version include multi packages, so you must include those packages when you upgrade:
RP/0/RP0/CPU0:R31#show ins ac sum
Fri Mar 29 02:35:01.477 UTC
Active Packages: 9
ncs5500-xr-6.6.1 version=6.6.1 [Boot image]
ncs5500-isis-2.1.0.0-r661
ncs5500-li-1.0.0.0-r661
ncs5500-mcast-2.1.0.0-r661
ncs5500-mpls-2.1.0.0-r661
ncs5500-mpls-te-rsvp-3.1.0.0-r661
ncs5500-ospf-2.0.0.0-r661
ncs5500-mgbl-3.0.0.0-r661
ncs5500-k9sec-3.1.0.0-r661
Check Storage Space
Whether harddisk/disk have enough space, please remove unuse file and tem file in disk/harddisk
完整阅读
12月 27th, 2014
什么是dummy vlan?
由于EVC平台在入端口可以通过rewrite命令剥离VLAN tag,这样导致在PW中没有任何tag,在Type 4时会有问题,两边VLAN的QOS无法传递给对端,所以就有了这个所谓的dummy vlan,它不是一个真正的VLAN,他只是传递一些QOS字段并且占一个位。那么dummy VLAN长什么样?其实大鹏之前的文章里已经详细介绍了EVC的各种行为,我这里只是介绍抓dummy VLAN的“心路历程”以及dummy VLAN的“样子”~
测试Topology:
起始测试环境为VPLS BGP auto discovery + LDP Sig,在76的入向抓包

测试步骤
1. 默认Type 5,在CE1 ping 带cos 5,ASR9k-1在AC上不配置rewrite,透传的VLAN是否带着802.1p?根据抓包信息,正常带着802.1p,详细看“bgp-ldp-vlan-cos5.pcapng”;另外有个疑问,既然type 5支持VLAN透传,为什么还要Type 4?答案请看文章结束部分
完整阅读
4月 28th, 2014
什么是PWHE?Pseudowire Headend,它类似于BVI,由于BVI有很多限制,所以研发了PWHE,它会利用进口的硬件资源,从而执行更多硬件级别的feature,如进出QOS等,而且BVI在一台chassis上只能支持2000个,而PWHE则更多。
那么PWHW/BVI需要部署在什么场景下呢?如下图所示:

完整阅读
2月 13th, 2014
跟同事讨论了下关于*PVID_Inc的问题,收益颇丰!估计没几个人能悟出在VPLS中PVID_inc的真谛。
为了验证讨论的内容,特意做下面的实验:
Topology

天蓝色属于一个bridge-domain vplstest1000;而红色属于bridge-domain vplstest6002
本文只讨论天蓝色的bridge-domain!
测试目的
验证下为什么会有PVID_inc的问题出现,及抓包分析,用有力的证据来验证
完整阅读