No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

How to solve the VIS6000 FC port negotiation problem

Publication Date:  2012-10-09 Views:  25 Downloads:  0
Issue Description
When VIS6000 connecting with FC Switch or host by fiber, it may have negotiation problem and the corresponding VIS port indicator flicker all the time.
Alarm Information
Null
Handling Process
1. Check the physical link (The status is 1 means normal.)
VIS_7796_0:/OSM/ISM/CLI # osp_mml fc gs
|Speed: 1-1G,2-2G,4-4G
|Mode: 1-ini,2-tgt,3-both,4-m_ini,8-m_tgt,c-m_both
Link: 0-null, 1-good, 2-down wait, 3-down confirm
Port: 0 Speed:0[4] Mode:3 Link:1 Name:22000022a100dbac Bus: 5 Host:3 Sfp:4300 IO:155
Port: 1 Speed:0[2] Mode:3 Link:1 Name:22010022a100dbac Bus: 5 Host:4 Sfp:4300 IO:259
Port: 2 Speed:0[1] Mode:3 Link:3 Name:22020022a100dbac Bus: 5 Host:5 Sfp:4300 IO:0
Port: 3 Speed:0[1] Mode:2 Link:1 Name:22030022a100dbac Bus: 5 Host:0 Sfp:4300 IO:0
Port:10 Speed:0[4] Mode:3 Link:1 Name:22040022a100dbac Bus:11 Host:7 Sfp:4300 IO:81
Port:11 Speed:0[2] Mode:3 Link:1 Name:22050022a100dbac Bus:11 Host:8 Sfp:4300 IO:600
Port:12 Speed:0[4] Mode:3 Link:3 Name:22060022a100dbac Bus:11 Host:9 Sfp:4300 IO:0
Port:13 Speed:0[1] Mode:3 Link:2 Name:22070022a100dbac Bus:11 Host:13 Sfp:4300 IO:0
2. Pull out VIS fiber and plug it again after about 10s. Check whether negotiating successful.
3. Setting FC port as auto-negotiation mode by ISM or CLI. The CLI command is shown below:
chgfcspeed -c controller ID -i interface ID -p port ID -s 0
Take step 1 to check whether the link is normal. 
4. Reset VIS FC port in debug condition. (The port number is 0)
VIS_7796_0:/OSM/ISM/CLI # osp_mml fc pl 0
Login pool list:
INDEX PORT TYPE STATE REP WWNMAP SESSION UPTIME
0 22000022a101a017 1 6 1 1 0 1 5714
Total used 1, free 2559
Take step 1 to check whether the link is normal. 
Root Cause
In most cases, it is not the hardware problem, so modifying the corresponding parameters or reset port can solve it. 
Suggestions
Null

END