網(wǎng)絡工程師成長日記365-IBIS西安工程回憶錄

這是我的第365篇原創(chuàng)文章，記錄網(wǎng)絡工程師行業(yè)的點點滴滴，結交IT行業(yè)有緣之人

我的第一次真實工程經(jīng)歷
5.26日這一天我的心情是格外的興奮，激動。
因為我終于有機會去體驗真實的工程操作，這是我盼望已久的。
早上我起的比平常早一個多小時，準備了許久才滿懷希望的走出家門坐上公交車，不知道怎么搞得平時堵的不能動彈的馬路，那天格外的順暢。到了陽明國際，我看了看表時間不到七點（哈哈，來得真早）干脆就坐在門口等老大，一邊等我就一邊想會不會讓我親自上手操作呢，越想越興奮時間不知不覺已經(jīng)過去半個小時了。
剛好老大也來了，七點半（也挺早）因為那邊要求我們八點五十就要到達目的地，所以我倆不敢耽擱時間。

檢查好應該帶的東西，consle線，筆記本，交叉線等等，我，老大，楊工就急急忙忙的出發(fā)了，坐上車我們心里總想著讓車走快點恨不得車能飛起來，結果我們都傻眼了--堵車。
沒辦法我們只能祈禱路快點通，借著這個機會，老大讓我們看了上海聯(lián)通公司給我們發(fā)過來的工程需求，哇塞全是英文，
還好有老大他簡單給我們介紹了這次工程概況---為西安ibis酒店裝配一臺cisco的2811路由器，以及三個模塊（）并且在上邊配置MPLS ×××（這可是我第一次聽說，長了見識了，呵呵）。
聽著聽著已經(jīng)到了大差市，下了車我們就開始找地方，還好我對西安比較熟悉（嘿嘿），大概走了不到500米我突然看見一個大大牌子西安宜必思酒店。
我們到了，時間八點半剛剛好，想著馬上就能見到各式各樣的網(wǎng)絡設備及拓撲心理就一陣竊喜。
這時老大給酒店網(wǎng)絡管理員打電話，結果我們就更傻眼了，原來人家也堵車，哎呀?jīng)]辦法等吧。
九點十分，網(wǎng)管終于到了，再他的指引下我們來到ibis的機房。
進去以后，好冷（給設備降溫用的空調），機房不大但是很整齊，各式設備擺放的井井有條，經(jīng)過和網(wǎng)管的交談得知人家用的設備是一樣兩臺.......好有錢呀。
其中設備主要有cisco的2950交換機，電話交換機，以及中國電信贈送的華為交換機，協(xié)議轉換器，其中最引人注目的就是一臺和印度連接的juneper防火墻--這是我以前見都沒見過的東西，真是大飽了眼福。
接下來，我們從網(wǎng)管那里得知現(xiàn)在酒店通過網(wǎng)通的光纖和上海的總部進行直接的通信，這就是要用到2811路由器，還有聯(lián)通的協(xié)議轉換器（V.35接口）

工程正式開始，首先酒店方的網(wǎng)管打開了2811路由器的包裝箱，終于現(xiàn)出廬山真面目了。
拿到設備后老大讓我們檢查了設備數(shù)目和收貨單上是不是匹配（這是很重要的），其中包括三個模塊，兩根直通線，一根（一端是串行口一端是V.35）。
正當我們要裝模塊的時候，發(fā)現(xiàn)模塊已經(jīng)裝配好了（真是爽，可是又覺得遺憾少了親自裝配模塊的經(jīng)歷）。
打開筆記本電腦連上consle線，連上路由器的串行口，另一端接到了聯(lián)通光纖的協(xié)議轉換器上，一切準備妥當。
打開電源后，機器運行正常，登陸到超級終端后，show running 后發(fā)現(xiàn)路由器的基本配置已經(jīng)被上海的工程師刷到上邊了，并且運行了MPLS ××× ，show ip int brief后發(fā)現(xiàn)物理鏈路狀態(tài)已經(jīng)是UP了，可是我們發(fā)現(xiàn)二層協(xié)議是down的，因為是二層協(xié)議所以不存在路由協(xié)議，ip地址之類的問題。
那是什么原因呢，我們手動激活端口后，狀態(tài)up了之后又跳轉到down，經(jīng)過思考會不會是封裝格式不對，封裝成ppp后還是沒反應。

我們陷入了沉思，突然楊工說能不能把寄存器的值修改成0x2142，結果還是不行。
接下來，老大給上海的工程師打電話，對方說是兩端的速率不一致，要打電話和西安聯(lián)通線路工程師核實一下（因為酒店用的是512k，擔心ce端把線接到了2m的口上），很快人家回復沒問題。
我們排除了路由器的問題，物理連接的問題，后來老大說是要做打環(huán)測試，可是我們沒有現(xiàn)成的工具做不成的，這下可難住我們了，后經(jīng)過聯(lián)系聯(lián)通的線路工程師，說可能是線路出了問題。
不一會人家就過來了，經(jīng)過打環(huán)確認線路沒有問題，那會是什么問題呢，我都快崩潰了。
老大再次打電話給上海工程師，對方回復說是讓西安聯(lián)通數(shù)據(jù)部門ping一下pe到ce，我們想了二層協(xié)議沒up怎么會ping通。
又一次失敗了，已經(jīng)12點了，人家都去吃飯了可我們沒心思吃（其實我已經(jīng)餓得不行了）。
這時，聯(lián)通工程師建議我們先去吃飯，他再找找協(xié)轉的問題。

匆匆吃完飯，回到ibis酒店繼續(xù)討論，我都有點退縮的想法，就在這時聯(lián)通工程師帶來了好消息，說是協(xié)轉的速率跳線開關可能設置不對，拆下協(xié)轉我們驚奇的發(fā)現(xiàn)協(xié)轉背后還有幾組微小的跳線開關，我的天，經(jīng)過正確的設置后（調成512k），安轉好協(xié)轉后，二層協(xié)議立刻就up，show ip bgp ，show ip route后發(fā)現(xiàn)出現(xiàn)bgp路由信息，ping 對方的ip地址是通的。
我們高興得都蹦了起來，接下來進行了調試，一切正常，這時已經(jīng)是下午四點了。我們終于長舒了一口氣
這次工程經(jīng)歷，我不僅學到在學校學不到的知識，而且見到很多以前沒見過的設備。在
實際的工程中，我們會遇到一些非常棘手的問題，只要我們頭腦清醒的去回憶我們曾經(jīng)學到的知識，我相信沒有處理不了的問題。
這次工程經(jīng)歷使我認識到我自身知識的不足，再接下來的學習中，我要踏踏實實的掌握每一個知識點，原理。
只有這樣，才會在今后真正的工作中得心應手。

不能泄露商業(yè)信息，所以我就把不重要的配置給大家看看

ian02#show ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route

Gateway of last resort is 210.53.161.109 to network 0.0.0.0

210.52.135.0/30 is subnetted, 3 subnets

B 210.52.135.76 [20/0] via 210.53.161.109, 00:11:40
B 210.52.135.52 [20/0] via 210.53.161.109, 00:11:40
B 210.52.135.56 [20/0] via 210.53.161.109, 00:11:40
210.53.164.0/30 is subnetted, 1 subnets
B 210.53.164.100 [20/0] via 210.53.161.109, 00:11:40
210.53.167.0/30 is subnetted, 1 subnets
B 210.53.167.148 [20/0] via 210.53.161.109, 00:11:40
210.22.133.0/30 is subnetted, 1 subnets
B 210.22.133.64 [20/0] via 210.53.161.109, 00:11:41
B 203.8.5.0/24 [20/0] via 210.53.161.109, 00:11:41
210.53.209.0/30 is subnetted, 9 subnets
B 210.53.209.40 [20/0] via 210.53.161.109, 00:11:41
B 210.53.209.116 [20/0] via 210.53.161.109, 00:12:11
B 210.53.209.112 [20/0] via 210.53.161.109, 00:12:11
B 210.53.209.108 [20/0] via 210.53.161.109, 00:12:11
B 210.53.209.104 [20/0] via 210.53.161.109, 00:12:11
B 210.53.209.72 [20/0] via 210.53.161.109, 00:12:11
B 210.53.209.220 [20/0] via 210.53.161.109, 00:12:11
B 210.53.209.216 [20/0] via 210.53.161.109, 00:12:11
B 210.53.209.200 [20/0] via 210.53.161.109, 00:12:11
210.53.166.0/30 is subnetted, 1 subnets
B 210.53.166.144 [20/0] via 210.53.161.109, 00:12:11
210.53.161.0/30 is subnetted, 2 subnets
B 210.53.161.96 [20/0] via 210.53.161.109, 00:12:11
C 210.53.161.108 is directly connected, Serial0/0/0
210.52.146.0/30 is subnetted, 2 subnets
B 210.52.146.32 [20/0] via 210.53.161.109, 00:12:11
B 210.52.146.44 [20/0] via 210.53.161.109, 00:12:11
210.53.160.0/30 is subnetted, 2 subnets
B 210.53.160.88 [20/0] via 210.53.161.109, 00:12:12
B 210.53.160.32 [20/0] via 210.53.161.109, 00:12:12
210.52.130.0/30 is subnetted, 1 subnets
B 210.52.130.100 [20/0] via 210.53.161.109, 00:12:12
192.168.10.0/30 is subnetted, 1 subnets
B 192.168.10.0 [20/0] via 210.53.161.109, 00:12:12
210.52.144.0/30 is subnetted, 1 subnets
B 210.52.144.164 [20/0] via 210.53.161.109, 00:12:14
172.16.0.0/28 is subnetted, 1 subnets
B 172.16.234.224 [20/0] via 210.53.161.109, 00:12:14
172.19.0.0/16 is variably subnetted, 9 subnets, 3 masks
B 172.19.246.64/26 [20/0] via 210.53.161.109, 00:12:14
B 172.19.246.0/26 [20/0] via 210.53.161.109, 00:12:14
B 172.19.170.64/27 [20/0] via 210.53.161.109, 00:12:14
B 172.19.170.96/27 [20/0] via 210.53.161.109, 00:12:14
C 172.19.246.192/26 is directly connected, FastEthernet0/0
B 172.19.245.192/26 [20/0] via 210.53.161.109, 00:12:14
B 172.19.0.0/16 [20/0] via 210.53.161.109, 00:12:14
B 172.19.246.128/26 [20/0] via 210.53.161.109, 00:12:14
B 172.19.245.128/26 [20/0] via 210.53.161.109, 00:12:14
172.20.0.0/16 is variably subnetted, 30 subnets, 5 masks
B 172.20.108.192/26 [20/0] via 210.53.161.109, 00:12:14
B 172.20.96.192/26 [20/0] via 210.53.161.109, 00:12:15
B 172.20.97.192/26 [20/0] via 210.53.161.109, 00:12:15
B 172.20.100.192/26 [20/0] via 210.53.161.109, 00:12:15
B 172.20.101.192/26 [20/0] via 210.53.161.109, 00:12:15
B 172.20.98.224/27 [20/0] via 210.53.161.109, 00:12:15
B 172.20.66.192/28 [20/0] via 210.53.161.109, 00:12:15
B 172.20.108.128/26 [20/0] via 210.53.161.109, 00:12:15
B 172.20.97.128/26 [20/0] via 210.53.161.109, 00:12:16
B 172.20.98.128/26 [20/0] via 210.53.161.109, 00:12:16
B 172.20.100.128/26 [20/0] via 210.53.161.109, 00:12:16
B 172.20.102.80/28 [20/0] via 210.53.161.109, 00:12:16
B 172.20.108.64/26 [20/0] via 210.53.161.109, 00:12:16
B 172.20.109.64/26 [20/0] via 210.53.161.109, 00:12:16
B 172.20.96.64/26 [20/0] via 210.53.161.109, 00:12:16
B 172.20.98.64/26 [20/0] via 210.53.161.109, 00:12:16
B 172.20.100.64/26 [20/0] via 210.53.161.109, 00:12:16
B 172.20.101.64/26 [20/0] via 210.53.161.109, 00:12:16
B 172.20.102.64/29 [20/0] via 210.53.161.109, 00:12:16
B 172.20.102.96/27 [20/0] via 210.53.161.109, 00:12:16
B 172.20.104.0/24 [20/0] via 210.53.161.109, 00:12:16
B 172.20.105.0/24 [20/0] via 210.53.161.109, 00:12:16
B 172.20.108.0/26 [20/0] via 210.53.161.109, 00:12:16
B 172.20.96.0/26 [20/0] via 210.53.161.109, 00:12:16
B 172.20.99.0/24 [20/0] via 210.53.161.109, 00:12:17
B 172.20.100.0/26 [20/0] via 210.53.161.109, 00:12:17
B 172.20.101.0/26 [20/0] via 210.53.161.109, 00:12:17
B 172.20.64.0/24 [20/0] via 210.53.161.109, 00:12:17
B 172.20.65.0/24 [20/0] via 210.53.161.109, 00:12:17
B 172.20.66.0/24 [20/0] via 210.53.161.109, 00:12:17
210.53.162.0/30 is subnetted, 1 subnets
B 210.53.162.12 [20/0] via 210.53.161.109, 00:12:18
210.53.173.0/30 is subnetted, 1 subnets
B 210.53.173.156 [20/0] via 210.53.161.109, 00:12:18
58.0.0.0/30 is subnetted, 1 subnets
B 58.246.65.168 [20/0] via 210.53.161.109, 00:12:18
220.248.8.0/30 is subnetted, 1 subnets
B 220.248.8.60 [20/0] via 210.53.161.109, 00:12:18
57.0.0.0/16 is subnetted, 1 subnets
B 57.200.0.0 [20/0] via 210.53.161.109, 00:12:18
210.53.175.0/30 is subnetted, 1 subnets
B 210.53.175.176 [20/0] via 210.53.161.109, 00:12:18
210.52.140.0/30 is subnetted, 3 subnets
B 210.52.140.224 [20/0] via 210.53.161.109, 00:12:18
B 210.52.140.200 [20/0] via 210.53.161.109, 00:12:18
B 210.52.140.152 [20/0] via 210.53.161.109, 00:12:18
210.53.174.0/30 is subnetted, 2 subnets
B 210.53.174.104 [20/0] via 210.53.161.109, 00:12:18
B 210.53.174.184 [20/0] via 210.53.161.109, 00:12:18
210.52.139.0/30 is subnetted, 2 subnets
B 210.52.139.12 [20/0] via 210.53.161.109, 00:12:19
B 210.52.139.152 [20/0] via 210.53.161.109, 00:12:19
218.105.198.0/30 is subnetted, 1 subnets
B 218.105.198.184 [20/0] via 210.53.161.109, 00:12:19
210.52.137.0/30 is subnetted, 2 subnets
B 210.52.137.112 [20/0] via 210.53.161.109, 00:12:20
B 210.52.137.144 [20/0] via 210.53.161.109, 00:12:20
210.52.136.0/30 is subnetted, 1 subnets
B 210.52.136.100 [20/0] via 210.53.161.109, 00:12:20
B* 0.0.0.0/0 [20/0] via 210.53.161.109, 00:12:20

ian02#show ip bgp
BGP table version is 89, local router ID is 210.53.161.110
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete

Network Next Hop Metric LocPrf Weight Path
> 0.0.0.0 210.53.161.109 0 9929 17621 9929 ?
> 57.200.0.0/16 210.53.161.109 0 9929 17621 9929 ?
> 58.246.65.168/30 210.53.161.109 0 9929 17621 ?
> 172.16.234.224/28
210.53.161.109 0 9929 17621 ?
> 172.19.0.0 210.53.161.109 0 9929 17621 9929 ?
> 172.19.170.64/27 210.53.161.109 0 9929 9929 ?
> 172.19.170.96/27 210.53.161.109 0 9929 9929 ?
> 172.19.245.128/26
210.53.161.109 0 9929 9929 ?
> 172.19.245.192/26
210.53.161.109 0 9929 9929 ?
> 172.19.246.0/26 210.53.161.109 0 9929 9929 ?
> 172.19.246.64/26 210.53.161.109 0 9929 9929 ?
> 172.19.246.128/26
210.53.161.109 0 9929 9929 ?
> 172.19.246.192/26
Network Next Hop Metric LocPrf Weight Path
0.0.0.0 0 32768 ?
> 172.20.64.0/24 210.53.161.109 0 9929 17621 9929 ?
> 172.20.65.0/24 210.53.161.109 0 9929 17621 9929 ?
> 172.20.66.0/24 210.53.161.109 0 9929 17621 9929 ?
> 172.20.66.192/28 210.53.161.109 0 9929 17621 9929 ?
> 172.20.96.0/26 210.53.161.109 0 9929 9929 ?
> 172.20.96.64/26 210.53.161.109 0 9929 9929 ?
> 172.20.96.192/26 210.53.161.109 0 9929 9929 ?
> 172.20.97.128/26 210.53.161.109 0 9929 9929 ?
> 172.20.97.192/26 210.53.161.109 0 9929 9929 ?
> 172.20.98.64/26 210.53.161.109 0 9929 ?
> 172.20.98.128/26 210.53.161.109 0 9929 ?
> 172.20.98.224/27 210.53.161.109 0 9929 9929 ?
> 172.20.99.0/24 210.53.161.109 0 9929 9929 ?
> 172.20.100.0/26 210.53.161.109 0 9929 9929 i
> 172.20.100.64/26 210.53.161.109 0 9929 9929 ?
> 172.20.100.128/26
210.53.161.109 0 9929 9929 ?
> 172.20.100.192/26
210.53.161.109 0 9929 9929 ?
> 172.20.101.0/26 210.53.161.109 0 9929 9929 ?
> 172.20.101.64/26 210.53.161.109 0 9929 9929 ?
Network Next Hop Metric LocPrf Weight Path
> 172.20.101.192/26
210.53.161.109 0 9929 9929 ?
> 172.20.102.64/29 210.53.161.109 0 9929 9929 ?
> 172.20.102.80/28 210.53.161.109 0 9929 9929 ?
> 172.20.102.96/27 210.53.161.109 0 9929 9929 ?
> 172.20.104.0/24 210.53.161.109 0 9929 9929 ?
> 172.20.105.0/24 210.53.161.109 0 9929 9929 ?
> 172.20.108.0/26 210.53.161.109 0 9929 9929 ?
> 172.20.108.64/26 210.53.161.109 0 9929 9929 ?
> 172.20.108.128/26
210.53.161.109 0 9929 9929 ?
> 172.20.108.192/26
210.53.161.109 0 9929 9929 ?
> 172.20.109.64/26 210.53.161.109 0 9929 9929 ?
> 192.168.10.0/30 210.53.161.109 0 9929 17621 ?
> 203.8.5.0 210.53.161.109 0 9929 17621 ?
> 210.22.133.64/30 210.53.161.109 0 9929 17621 ?
> 210.52.130.100/30
210.53.161.109 0 9929 ?
> 210.52.135.52/30 210.53.161.109 0 9929 ?
> 210.52.135.56/30 210.53.161.109 0 9929 ?
> 210.52.135.76/30 210.53.161.109 0 9929 ?
Network Next Hop Metric LocPrf Weight Path
> 210.52.136.100/30
210.53.161.109 0 9929 ?
> 210.52.137.112/30
210.53.161.109 0 9929 ?
> 210.52.137.144/30
210.53.161.109 0 9929 9929 ?
> 210.52.139.12/30 210.53.161.109 0 9929 ?
> 210.52.139.152/30
210.53.161.109 0 9929 ?
> 210.52.140.152/30
210.53.161.109 0 9929 ?
> 210.52.140.200/30
210.53.161.109 0 9929 ?
> 210.52.140.224/30
210.53.161.109 0 9929 ?
> 210.52.144.164/30
210.53.161.109 0 9929 ?
> 210.52.146.32/30 210.53.161.109 0 9929 ?
> 210.52.146.44/30 210.53.161.109 0 9929 ?
> 210.53.160.32/30 210.53.161.109 0 9929 ?
> 210.53.160.88/30 210.53.161.109 0 9929 9929 ?
> 210.53.161.96/30 210.53.161.109 0 9929 ?
Network Next Hop Metric LocPrf Weight Path

• 210.53.161.108/30
  210.53.161.109 0 0 9929 ?
  > 0.0.0.0 0 32768 ?
  > 210.53.162.12/30 210.53.161.109 0 9929 ?
  > 210.53.164.100/30
  210.53.161.109 0 9929 ?
  > 210.53.166.144/30
  210.53.161.109 0 9929 ?
  > 210.53.167.148/30
  210.53.161.109 0 9929 ?
  > 210.53.173.156/30
  210.53.161.109 0 9929 ?
  > 210.53.174.104/30
  210.53.161.109 0 9929 ?
  > 210.53.174.184/30
  210.53.161.109 0 9929 ?
  > 210.53.175.176/30
  210.53.161.109 0 9929 ?
  > 210.53.209.40/30 210.53.161.109 0 9929 ?
  > 210.53.209.72/30 210.53.161.109 0 9929 ?
  > 210.53.209.104/30
  210.53.161.109 0 9929 ?
  Network Next Hop Metric LocPrf Weight Path
  > 210.53.209.108/30
  210.53.161.109 0 9929 ?
  > 210.53.209.112/30
  210.53.161.109 0 9929 ?
  > 210.53.209.116/30
  210.53.161.109 0 9929 ?
  > 210.53.209.200/30
  210.53.161.109 0 9929 ?
  > 210.53.209.216/30
  210.53.161.109 0 9929 ?
  > 210.53.209.220/30
  210.53.161.109 0 9929 ?
  > 218.105.198.184/30
  210.53.161.109 0 9929 ?
  > 220.248.8.60/30 210.53.161.109 0 9929 17621 ?

xian02#show run
Building configuration...

Current configuration : 3761 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname xian02
!
boot-start-marker
boot system flash:c2800nm-advipservicesk9-mz.124-15.T1.bin
boot-end-marker
!
logging buffered 51200 warnings
!
no aaa new-model
!
!
ip cef
!
!
no ip domain lookup
ip domain name yourdomain.com
!
multilink bundle-name authenticated
!
!
voice-card 0
no dspfarm
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
username cisco privilege 15 secret 5 $1$FdBh$L/DhUve5DwBuACS61BMWm0
archive
log config
hidekeys
!
!
!
!
!
!
interface Loopback0
no ip address
!
interface FastEthernet0/0
description IBIS xian02
ip address X.X.X.X 255.255.255.192
ip access-group To_SHAccor_In in
duplex auto
speed auto
!
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
interface Serial0/0/0
description MPLS ×××
bandwidth 512
ip address X.X.X.X 255.255.255.252
no fair-queue
!
interface BRI0/1/0
no ip address
encapsulation hdlc
shutdown
!
interface BRI0/2/0
no ip address
encapsulation hdlc
shutdown
!
router bgp 65086
no synchronization
bgp log-neighbor-changes
redistribute connected
redistribute static
neighbor X.X.X.X remote-as 9929
no auto-summary
!
!
!
no ip http server
ip http access-class 23
ip http authentication local
no ip http secure-server
ip http timeout-policy idle 60 life 86400 requests 10000
!
ip access-list extended To_SHAccor_In
permit ip any 57.0.0.0 0.255.255.255
permit ip any 172.19.0.0 0.0.255.255
permit ip any 172.20.66.0 0.0.0.255
permit ip any 172.20.65.0 0.0.0.255
permit ip any host 172.20.89.33
!
access-list 23 permit 10.10.10.0 0.0.0.7
!
!
!
!
!
!
control-plane
!
!
!
!
!
!
!
!
!
banner exec ^C
% Password expiration warning.

Cisco Router and Security Device Manager (SDM) is installed on this device and
it provides the default username "cisco" for one-time use. If you have already
used the username "cisco" to login to the router and your IOS image supports the
"one-time" user option, then this username has already expired. You will not be
able to login to the router with this username after you exit this session.

It is strongly suggested that you create a new username with a privilege level
of 15 using the following command.

username <myuser> privilege 15 secret 0 <mypassword>

Replace <myuser> and <mypassword> with the username and password you want to
use.

---

^C
banner login ^C

Cisco Router and Security Device Manager (SDM) is installed on this device.
This feature requires the one-time use of the username "cisco"
with the password "cisco". The default username and password have a privilege level of 15.

Please change these publicly known initial credentials using SDM or the IOS CLI.
Here are the Cisco IOS commands.

username <myuser> privilege 15 secret 0 <mypassword>
no username cisco

Replace <myuser> and <mypassword> with the username and password you want to use.

For more information about SDM please follow the instructions in the QUICK START
GUIDE for your router or go to http://www.cisco.com/go/sdm

^C
!
line con 0
exec-timeout 0 0
logging synchronous
login local
line aux 0
line vty 0 4
access-class 23 in
exec-timeout 30 0
privilege level 15

login
transport input all
line vty 5 15
access-class 23 in
exec-timeout 30 0
privilege level 15

login
transport input telnet
!
scheduler allocate 20000 1000

!
web*** cef
!
end

轉載于:https://blog.51cto.com/13448371/2072498

總結

以上是生活随笔為你收集整理的网络工程师成长日记365-IBIS西安工程回忆录的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網(wǎng)站內容還不錯，歡迎將生活随笔推薦給好友。