n5k:
feature fex (功能打開)
interface Ethernet1/1
switchport mode fex-fabric
fex associate 100
完成
attach fex 100就可以連到n2k
2013年6月26日 星期三
firewall lab
router 必備指令
firewall module 4 vlan-group 300,400,2262
firewall vlan-group 300 15,21-29,26,2262,
vtp mode transparent
!
vlan 2262
!
interface FastEthernet8/13
no ip address
switchport
switchport access vlan 2262
switchport mode access
!
!
interface Vlan2262
ip address 10.97.254.60 255.255.255.248
ip route-cache flow
shutdown
!
/hw-module module 1 reset
/這個是用來reset module
/firewall上 dir flash:
/asdm
/image
/star-config
icmp permit any ___ (vlan的nameif)
這樣才ping的到
http server enable
http ip submask ___(vlan的nameif)
這樣才可以用網頁開啟ASDM
這樣就可以用asdm了吧...
firewall module 4 vlan-group 300,400,2262
firewall vlan-group 300 15,21-29,26,2262,
vtp mode transparent
!
vlan 2262
!
interface FastEthernet8/13
no ip address
switchport
switchport access vlan 2262
switchport mode access
!
!
interface Vlan2262
ip address 10.97.254.60 255.255.255.248
ip route-cache flow
shutdown
!
/hw-module module 1 reset
/這個是用來reset module
/firewall上 dir flash:
/asdm
/image
/star-config
icmp permit any ___ (vlan的nameif)
這樣才ping的到
http server enable
http ip submask ___(vlan的nameif)
這樣才可以用網頁開啟ASDM
這樣就可以用asdm了吧...
2013年6月22日 星期六
2013 F1-日本站門票
2013 F1 日本站 門票 !!!!!!!!!!!!!!!!!!
6張 220,000日幣的門票收到了!!(終於)
-------------
簡單描述購買歷程
1.4月初臨時想去看F1,所以就決定衝了&開始找資料研究
2.ptt有人開團,V1區原價 62,000日幣,一次購買6張的話只要 37,000日幣!!!
3.但是我慢了一步沒跟到
4.所以自己開團,幸運的湊滿人數
5.找認識的幫忙買,但是沒有,所以找了代買,有找到
6.一次把票價所有金額匯給代買(22萬日幣,沒下標&不認識&心臟大顆!?)
7.代買直接從suzuka官網訂購,再寄到他家(他住東京)
8.訂購完後,官網mail來信說6月中才會寄出
9.漫長的等待(煎熬)
10.收到
-------------
小殘念就是...怎不是卡片....11年就有...人家新加坡站好像也有
costdown也不要這樣.....好歹也花了那麼多錢買
6張 220,000日幣的門票收到了!!(終於)
-------------
簡單描述購買歷程
1.4月初臨時想去看F1,所以就決定衝了&開始找資料研究
2.ptt有人開團,V1區原價 62,000日幣,一次購買6張的話只要 37,000日幣!!!
3.但是我慢了一步沒跟到
4.所以自己開團,幸運的湊滿人數
5.找認識的幫忙買,但是沒有,所以找了代買,有找到
6.一次把票價所有金額匯給代買(22萬日幣,沒下標&不認識&心臟大顆!?)
7.代買直接從suzuka官網訂購,再寄到他家(他住東京)
8.訂購完後,官網mail來信說6月中才會寄出
9.漫長的等待(煎熬)
10.收到
-------------
小殘念就是...怎不是卡片....11年就有...人家新加坡站好像也有
costdown也不要這樣.....好歹也花了那麼多錢買
2013年6月18日 星期二
2013年6月5日 星期三
Cisco Supervisor 720 fail log
難得遇到Core 卡版故障,記錄一下這次故障log
Supervisor Engine 720
Mod Ports Card Type Model Serial No.
--- ----- --------------------------------- ------------------ -----------
5 5 Supervisor Engine 720 VS-S720-10G 123456789
Mod MAC addresses Hw Fw Sw Status
--- ------------------------- ------ ------------ ------------ -------
5 123456789 0.0 0.0(0) 0.0(0) MinFail
Mod Sub-Module Model Serial Hw Status
---- --------------------------- ---------------- ----------- ------- -------
5 Policy Feature Card VS-F6K 123 0.0 MinFail
5 MSFC3 Daughterboard VS-F6K 123 0.0 MinFail
開機Status 從原本的OK過一下子後變成MinFail 後在過一下子變成MajFail
除此之外 show env 還會帶出alarm info
Router#sh env
environmental alarms:
system minor alarm on fan-tray 1 fan-fail (raised 00:01:35 ago)
system minor alarm on module 5 EARL outlet temperature (raised 00:01:02 ago)
...
..
.
show log
show module
sh env
Supervisor Engine 720
Mod Ports Card Type Model Serial No.
--- ----- --------------------------------- ------------------ -----------
5 5 Supervisor Engine 720 VS-S720-10G 123456789
Mod MAC addresses Hw Fw Sw Status
--- ------------------------- ------ ------------ ------------ -------
5 123456789 0.0 0.0(0) 0.0(0) MinFail
Mod Sub-Module Model Serial Hw Status
---- --------------------------- ---------------- ----------- ------- -------
5 Policy Feature Card VS-F6K 123 0.0 MinFail
5 MSFC3 Daughterboard VS-F6K 123 0.0 MinFail
開機Status 從原本的OK過一下子後變成MinFail 後在過一下子變成MajFail
除此之外 show env 還會帶出alarm info
Router#sh env
environmental alarms:
system minor alarm on fan-tray 1 fan-fail (raised 00:01:35 ago)
system minor alarm on module 5 EARL outlet temperature (raised 00:01:02 ago)
...
..
.
show log
show module
sh env
Cisco IOS IP Service Level Agreements (SLAs)
ip sla 2
icmp-echo x.x.x.x source-ip y.y.y.y 從Y 去ping X是否正常
ip sla schedule 2 life forever start-time now
ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}] [ageout seconds] [recurring]
track 2 ip sla 2 reachability
這行還不懂
ip route x x x track 2
ip route x x x
sh ip route x
sh ip sla statistics
原本有2條線,新增一條專線上做這些的設定
參考內容(有時間在看....)
Cisco IOS IP Service Level Agreements (SLAs)
麟瑞科技-Cisco IP SLA協助您了解網路效能
砍筆閣-IP SLA 設定
Cisco Source-ip through vrf
icmp-echo x.x.x.x source-ip y.y.y.y 從Y 去ping X是否正常
ip sla schedule 2 life forever start-time now
ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}] [ageout seconds] [recurring]
track 2 ip sla 2 reachability
這行還不懂
ip route x x x track 2
ip route x x x
sh ip route x
sh ip sla statistics
原本有2條線,新增一條專線上做這些的設定
參考內容(有時間在看....)
Cisco IOS IP Service Level Agreements (SLAs)
麟瑞科技-Cisco IP SLA協助您了解網路效能
砍筆閣-IP SLA 設定
Cisco Source-ip through vrf
Cisco N5K FEX N2K error & reload ?!
名詞解釋 fex = fabric extender 翻譯: 光纖....延伸/擴充器?!
Vntag 好像是 802.1Qbh
沒記錯的話FEX設定是這樣
在N5K上設定就好
狀況:
N5K 透過FEX 接一台N2K, 但是N2K其中之一的Power Supply掛掉,
整台N2K月重啟,這是不正常&不合理的
**重啟之前port-channel 先斷線
**另外找了設備做LAB就沒出現這問題,
就是Power 掛掉其中一個並不會影響N2K運作,也不會重啟
目前偏向是N2K的問題(過程不解釋)
在N2K上 show fex 1xx detail 看到記錄
xx:xx:xx.645011: Deleting route to FEX
xx:xx:xx.652318: Module disconnected
xx:xx:xx.653917: Offlining Module
xx:xx:xx.654693: Module Offline Sequence
xx:xx:xx.803507: Module Offline
xx:xx:xx.878381: Module register received
xx:xx:xx.889902: Registration response sent
xx:xx:xx.544625: Module Online Sequence
xx:xx:xx.203926: Module Online
N5K的Log
xx:xx:48.619116: Interface Down
xx:xx:48.619270: Switching to non-Vntag mode
xx:xx:48.619678: State changed to: Disconnected
xx:xx:50.562693: fport memberdown retry end: sending out resp
xx:xx:50.659788: Satellite disconnected. Unbind msg sent
xx:xx:50.660177: State changed to: Configured
xx:xx:50.824645: Port removed from port-channel
xx:xx:50.825953: fport phy cleanup retry end: sending out resp
xx:xx:50.828176: pre config: is a port-channel member
xx:xx:50.828185: Port added to port-channel
xx:xx:50.828319: Remote-chassis configured
xx:xx:50.828397: Port changed to fabric mode
xx:xx:56.173563: Interface Up
xx:xx:56.173645: Started SDP
xx:xx:56.174048: State changed to: Fabric Up
xx:xx:56.176631: Port Bringup rcvd
xx:xx:57.989624: Fcot message sent to Ethpm
xx:xx:57.990738: Fcot response received. SFP valid
xx:xx:57.990805: Advertizing Vntag
xx:xx:57.991343: State changed to: Connecting
xx:xx:58.121131: Satellite connected. Bind msg sent
xx:xx:58.121701: fport bringup retry end: sending out resp
xx:xx:58.127071: State changed to: Active
xx:xx:58.231651: Bundle member bringup rcvd
xx:xx:58.236811: fport memberup retry end: sending out resp
除了show log 或detail 還有下列指令可以看到一些有用的訊息(也許)
Attach fex 1xx
show logging onboard exception-log
show logging onboar internal reset-reason
show logging onboar environmental-history
show logging onboar obfl-history
show logging onboar internal kernel
在N5K上
show platform software ethpc event-history interface Ethx/x
show platform software ethpc event-history interface Ethx/x
show system internal ethpm ev ent-history interface ex/x
show system internal ethpm ev ent-history interface ex/x
補充...
1.
這問題還沒解決
2.
在N2K 上show tech 有這內容
Event:E_DEBUG,
xx:xx:xx 2013 (Warning) unexpected mts msg (opcode - 125974)
3.
在有問題的N2K上執行這指令,telnet會斷線(telnet will be down)
show logging onboar internal reset-reason
show system reset-reason
<也是因為這因素所以猜測這台N2K有問題>
Vntag 好像是 802.1Qbh
沒記錯的話FEX設定是這樣
在N5K上設定就好
switch# configure terminal switch(config)# interface ethernet x/x switch(config-if)# switchport mode fex-fabric switch(config-if)# fex associate 1xx
狀況:
N5K 透過FEX 接一台N2K, 但是N2K其中之一的Power Supply掛掉,
整台N2K月重啟,這是不正常&不合理的
**重啟之前port-channel 先斷線
**另外找了設備做LAB就沒出現這問題,
就是Power 掛掉其中一個並不會影響N2K運作,也不會重啟
目前偏向是N2K的問題(過程不解釋)
在N2K上 show fex 1xx detail 看到記錄
xx:xx:xx.645011: Deleting route to FEX
xx:xx:xx.652318: Module disconnected
xx:xx:xx.653917: Offlining Module
xx:xx:xx.654693: Module Offline Sequence
xx:xx:xx.803507: Module Offline
xx:xx:xx.878381: Module register received
xx:xx:xx.889902: Registration response sent
xx:xx:xx.544625: Module Online Sequence
xx:xx:xx.203926: Module Online
N5K的Log
xx:xx:48.619116: Interface Down
xx:xx:48.619270: Switching to non-Vntag mode
xx:xx:48.619678: State changed to: Disconnected
xx:xx:50.562693: fport memberdown retry end: sending out resp
xx:xx:50.659788: Satellite disconnected. Unbind msg sent
xx:xx:50.660177: State changed to: Configured
xx:xx:50.824645: Port removed from port-channel
xx:xx:50.825953: fport phy cleanup retry end: sending out resp
xx:xx:50.828176: pre config: is a port-channel member
xx:xx:50.828185: Port added to port-channel
xx:xx:50.828319: Remote-chassis configured
xx:xx:50.828397: Port changed to fabric mode
xx:xx:56.173563: Interface Up
xx:xx:56.173645: Started SDP
xx:xx:56.174048: State changed to: Fabric Up
xx:xx:56.176631: Port Bringup rcvd
xx:xx:57.989624: Fcot message sent to Ethpm
xx:xx:57.990738: Fcot response received. SFP valid
xx:xx:57.990805: Advertizing Vntag
xx:xx:57.991343: State changed to: Connecting
xx:xx:58.121131: Satellite connected. Bind msg sent
xx:xx:58.121701: fport bringup retry end: sending out resp
xx:xx:58.127071: State changed to: Active
xx:xx:58.231651: Bundle member bringup rcvd
xx:xx:58.236811: fport memberup retry end: sending out resp
除了show log 或detail 還有下列指令可以看到一些有用的訊息(也許)
Attach fex 1xx
show logging onboard exception-log
show logging onboar internal reset-reason
show logging onboar environmental-history
show logging onboar obfl-history
show logging onboar internal kernel
在N5K上
show platform software ethpc event-history interface Ethx/x
show platform software ethpc event-history interface Ethx/x
show system internal ethpm ev ent-history interface ex/x
show system internal ethpm ev ent-history interface ex/x
補充...
1.
這問題還沒解決
2.
在N2K 上show tech 有這內容
Event:E_DEBUG,
xx:xx:xx 2013 (Warning) unexpected mts msg (opcode - 125974)
3.
在有問題的N2K上執行這指令,telnet會斷線(telnet will be down)
show logging onboar internal reset-reason
show system reset-reason
<也是因為這因素所以猜測這台N2K有問題>
2013年6月4日 星期二
申請AdSense 帳戶復權被打槍
歐....申請AdSense 帳戶復權被打槍了
|
6月x日 (x 天以前)
| |||
|
感謝您申訴時提供的額外資料,我們十分感激您持續對 Adsense 計畫抱持興趣。在徹底審查您的帳戶資料並考量您的意見後,我們的
若您需要關於無效活動政策或審查過程的詳細資訊,請造訪 http://www.google.com/adsense/
提醒您,被停權的發佈商帳戶不得再參與 Adsense 計畫。感謝您的理解,Google AdSense 小組
好啦,被鎖的原因是因為以前有手動點過廣告.
沒什麼好說的,就這樣囉.
訂閱:
文章 (Atom)