NAT-MCH Users Manual Version 1.16

NAT-MCH – Users Manual
IP address source GbE board
(**)
Source of the MCHs own IP address on the Gigabit
configuration Ethernet port.
Valid options are:
• board configuration –saved value from local
EEPROM – see chap. 5.3
• DHCP
• ShM Link record – IP address is taken from
Carrier FRU device, Shelf FRU info record
•
(**)
CM IP link record – IP address is taken from
Carrier FRU device, Carrier FRU info record
RMCP session activity timeout 0 min Timeout for remote RMCP sessions being inactive –
minutes
minutes
RMCP session activity timeout 60 sec Timeout for remote RMCP sessions being inactive –
seconds
seconds
Default Fan Level 30% Default fan level in percent after power up.
A value of 0 remains the default value of the cooling
unit active.
Enable backward compatibility No Enables backward compatibility to firmware version
less or equal V2.4. If this mode is enabled CM and
ShM behave as to use common SDR repository and
SEL and single bridged IPMI messages are directly
delivered to the target devices (PMs, CUs, AMCs,
Clock/HUB modules). If this mode is disabled single
bridged IPMI messages are delivered to the CM and
target devices have to be accessed using double
bridged IPMI messages which will be extracted first
by the ShM and then by the CM.
Remark (*)
An external Shelf or System Manager can be connected to the NAT-MCH by an Ethernet connection running the
RMCP protocol.
By default the management port is routed to the front panel 100 BaseT port.
Alternatively the management port can be switched to one link of the onboard GbE Switch. If the management
port resides on the GbE switch, it can either be connected to an external shelf- or system manager by the GbE
uplink port, or to any shelf or system controller running on one of the AMC modules, connected to the MCH by
a GbE backplane link.
Remark (**)
Although it is possible to configure both the management and the gigabit Ethernet ports to obtain its IP
configuration from DHCP it does not make sense because both Ethernet interfaces then will be located in the
same subnet and it is not clear to which physical interface packets are routed. Such a configuration will lead to
discarding of packets.
Also note that DHCP is only allowed for the Ethernet port that is used for the management interface (refer to the
option ‘Management interface at GbE port’). This means if the option ‘Management interface at GbE port’ is set
to disabled DHCP can only be used for the ‘IP address source Mgmt’, if the option is enabled DHCP can only be
used for the ‘IP address source GbE’.
Version 1.16 © N.A.T. GmbH 33