Domain Controller 0xFFFCDA or 0xDAFFFC?

Answered Question
Sep 21st, 2009

to fcping a domain controller in domain DA, VSAN 100, you do:

fcping fcid 0xFFFCDA vsan 100

why is the address not instead DAFFFC? Are there any other commands or rules to follow of when to put the domain at the end of an FCID instead of the beginning?

Thanks,

Brian

I have this problem too.
0 votes
Correct Answer by Michael Brown about 7 years 2 months ago

Control traffic between switches always uses the Distributed Server Addressing model where the domain number is the last byte, with the middle byte indicates the service.

To ping the Domain DA controller the destination address is 0xfffcda.

There are no other situations that I know of where you would need to know about the domain at the end of the FCID...if you see a trace with frames like this, it's good to know how the address scheme works.

When a domain controller learns of a newly attached device on another switch, it may source a frame from 0xfffcda (da is the domain id here) to that new device as part of a discovery process. It's helpful to know that the switch that send the frame is using a for it's domain id. you may see this on the ISL between switches...or on the link to the device itself.

The only time a frame would have a destination address of 0xFFFFFC is if was a directly attached device sending a frame to the local name server. IE: registering capabilities.

Hope this helps,

Mike

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
Michael Brown Tue, 09/22/2009 - 12:02

Control traffic between switches always uses the Distributed Server Addressing model where the domain number is the last byte, with the middle byte indicates the service.

To ping the Domain DA controller the destination address is 0xfffcda.

There are no other situations that I know of where you would need to know about the domain at the end of the FCID...if you see a trace with frames like this, it's good to know how the address scheme works.

When a domain controller learns of a newly attached device on another switch, it may source a frame from 0xfffcda (da is the domain id here) to that new device as part of a discovery process. It's helpful to know that the switch that send the frame is using a for it's domain id. you may see this on the ISL between switches...or on the link to the device itself.

The only time a frame would have a destination address of 0xFFFFFC is if was a directly attached device sending a frame to the local name server. IE: registering capabilities.

Hope this helps,

Mike

Actions

This Discussion

 

 

Trending Topics: Storage Networking