6 Indium

Is changing the FCID from dynamic to static disruptive for HP-UX?

Jump to solution

The currect FCID is dynamically assigned to (some of) our HP-UX machines. I'd like to change this FCID to static, but when I do so, will the HP-UX notice anything of this change ?

In other words: is changing the FCID setting from Dynamic to Static nondisruptive or not ?

0 Kudos
1 Solution

Accepted Solutions
7 Thorium

Re: Is changing the FCID from dynamic to static disruptive for HP-UX?

Jump to solution

you did not pay attention to what i highlighted in my previous post, did you  ?

FCID persistence can be set at VSAN level, instead of setting it for each individual WWN.

fcdomain fcid persistent vsan 10

after making that change, i think you will need to restart fcdomain and that might be disruptive.

fcdomain restart vsan 10

View solution in original post

8 Replies
7 Thorium

Re: Is changing the FCID from dynamic to static disruptive for HP-UX?

Jump to solution

so right now this field is set to disabled for that VSAN ?

9134# sh fcdomain vsan 10

The local switch is the Principal Switch.

Local switch run time information:

        State: Stable

        Local switch WWN:    20:0a:00:0d:ec:94:9e:c1

        Running fabric name: 20:0a:00:0d:ec:94:9e:c1

        Running priority: 1

        Current domain ID: 0x9b(155)

Local switch configuration information:

        State: Enabled

       FCID persistence: Enabled

        Auto-reconfiguration: Disabled

        Contiguous-allocation: Disabled

        Configured fabric name: 20:01:00:05:30:00:28:df

        Optimize Mode: Disabled

        Configured priority: 1

        Configured domain ID: 0x9b(155) (static)

6 Indium

Re: Is changing the FCID from dynamic to static disruptive for HP-UX?

Jump to solution

I'm not asking about the domain id, but I'm asking about setting the FCID to static instead of dynamic.

for example: on the commandline this example says:

fcdomain fcid database

  vsan 150 wwn 50:01:43:80:05:68:e7:d8 fcid 0x340000

In the GUI it says "static" behind the 0x340000, where other hosts are set to dynamic. So that one's ok. The HP-UX that's still set to dynamic needs to be set to fixed and I'm wondering if this is nondisruptive for the host

0 Kudos
6 Indium

Re: Is changing the FCID from dynamic to static disruptive for HP-UX?

Jump to solution

or can FCID persistence now be enabled on a switch level instead of per wwn ?

0 Kudos
7 Thorium

Re: Is changing the FCID from dynamic to static disruptive for HP-UX?

Jump to solution

you did not pay attention to what i highlighted in my previous post, did you  ?

FCID persistence can be set at VSAN level, instead of setting it for each individual WWN.

fcdomain fcid persistent vsan 10

after making that change, i think you will need to restart fcdomain and that might be disruptive.

fcdomain restart vsan 10

View solution in original post

7 Thorium

Re: Is changing the FCID from dynamic to static disruptive for HP-UX?

Jump to solution

btw ..i thought persistent fcid was on by default ?

0 Kudos
6 Indium

Re: Is changing the FCID from dynamic to static disruptive for HP-UX?

Jump to solution

I wasn't aware of this option to be set on the VSAN level. I assumed it still had to be done at the wwn level. Thanks for the reminder about the highlighted text

0 Kudos
Not applicable

Re: Is changing the FCID from dynamic to static disruptive for HP-UX?

Jump to solution

Hi RRR

Could you please tell me how did you work to set Persistent FCID while migrating from Cisco to Brocade.

0 Kudos
6 Indium

Re: Is changing the FCID from dynamic to static disruptive for HP-UX?

Jump to solution

It was a while back, but I think it was done by writing down the old FCIDs and looking up matching FCIDs on the new Brocade and physically connecting the patch cables to that port, since in Brocade you can't change the FCID.

0 Kudos