Kontron MS1300 Series Application Note Download Page 3

MS1300   Getting Started | VLAN-segregated Management and Payload Networks

 

 

www.symkloud.com 

 

// 3 

 

1/

 

Introduction 

The factory default network configuration of the MS1300 platform assigns the management traffic to VLAN 4093 and the 
payload data traffic to VLAN 1. Both traffic flows are received and sent untagged (without 802.1Q VLAN tags) on the 
corresponding external ports (the management port and the uplink port of the hub). 

The switch with shelf management controller (ShMC) is referred to as a hub in this document. 

 

This  use  case  describes  the  network  integration  steps  to  get  started  with  the  MS1300  platform  where  the  traffic 
(management and payload data) passes over two different network links that are segregated either by VLAN from 
a  single  switch  or  from  two  different  switches  that  are  physically  interconnected.  The target configuration is 
rather similar to the default configuration but is different in that it requires mandatory spanning-tree configurations 
in order to guarantee a loop-free topology. Additionally, in order to be closer to real cases, the payload data traffic is 
changed to a different VLAN. The ports corresponding to the management link and the payload data uplink are both 
configured as 802.1Q trunk interfaces. 

 

The steps described in this use case assume that the MS1300 has default configurations loaded in all its elements 
(factory default). 

Kontron created other use cases related to the MS1300 network configuration. You may refer to them if you want to:  

 

Create a common network for management and payload traffic 

 

This  use  case  describes  the  network  integration  steps  to  get  started  with  the  MS1300  platform  when  the  factory 
default network settings need to be changed to have all traffic (management and payload data) passing over the same 
network uplink. 

 

Create physically isolated management and payload networks 

 

This  use  case  describes  the  network  integration  steps  to  get  started  with  the  MS1300  platform  where  the  traffic 
(management  and  payload  data)  passes  over  two  network  links  from  two  different  switches  that  are  physically 
isolated. This is similar to the default configuration of the MS1300 when the payload data traffic is kept on VLAN 1. For 
this  use  case,  in  order  to  be  closer  to  real  cases,  the  payload  data  traffic  is  changed  to  a  different  VLAN  and  the 
corresponding uplink is configured as 802.1Q trunk interface. The traffic on the management link is kept untagged. 

Summary of Contents for MS1300 Series

Page 1: ... APPLICATION NOTE www symkloud com 1 MS1300 Getting Started VLAN segregated Management and Payload Networks AN18008 Doc Rev 1 0 ...

Page 2: ...uration Management Network 16 4 7 Connect the MS1300 Platform to the Network Payload Data Network 16 4 8 Confirm Proper Networking Configuration Spanning Tree 16 4 9 Confirm Proper Networking Configuration Payload Data Network 17 5 Management Configuration 18 5 1 Set Up Access to the ShMC 18 5 2 Configure the MSH8900 ShMC and the BMC FRU0 on Each MSP Node Static IP Source 19 5 3 Configure the MSH8...

Page 3: ...ent VLAN The ports corresponding to the management link and the payload data uplink are both configured as 802 1Q trunk interfaces The steps described in this use case assume that the MS1300 has default configurations loaded in all its elements factory default Kontron created other use cases related to the MS1300 network configuration You may refer to them if you want to Create a common network fo...

Page 4: ...n note contains an introduction with general information followed by steps to perform platform configuration The sections covered are shown in black on the flow diagram below 1 1 Platform Architecture The architecture and components of an MS1300 platform are similar to those of a rack in a data center The platform contains the equivalent of 1 top of rack ToR switch and up to 6 servers internally i...

Page 5: ...egated Management and Payload Networks www symkloud com 5 Each individual modular server processing node MSP node has network connections to the switch Figure 2 MS1300 management interconnections Figure 3 Rack architecture equivalence ...

Page 6: ...ial console RJ45 port 1010 3 4 10GbE SFP uplink port 1 2 5 Quad GbE RJ45 uplink ports 3 4 5 6 6 ID LED Blue Payload power removed On Identify command in progress Blinking Payload power is on Off None 7 Power LED Green Payload power is on On Hub hosts the active ShMC On Payload power removed Off None 8 Status LED Amber Hub transitioning when power button pressed clean shutdown request Blinking Hub ...

Page 7: ...MS1300 Getting Started VLAN segregated Management and Payload Networks www symkloud com 7 Figure 5 Factory default IP addresses ...

Page 8: ...the PVST based ToR switches on the interfaces that will interconnect to the MS1300 By completing the steps described in this section you will configure your switch in order to be ready to connect the MS1300 platform to your network infrastructure Once the network cable is connected to the platform you will have the ability to access the switch management interface Prior to performing the steps des...

Page 9: ... FRU0 MSP node 2 BMC IP FRU0 MSP node 3 BMC IP FRU0 192 168 101 1 24 192 168 101 10 24 192 168 101 11 24 192 168 101 12 24 192 168 101 13 24 Hub management IP System monitor Web GUI Switch IP MSP node BMC IP Management ToR switch IP 192 168 101 254 2 4 This IP is used for example purposes in the configuration shown for this use case It represents the IP of your Management ToR switch Management ToR...

Page 10: ...er global configuration mode Configure spanning tree mode to PVST Enable extend system id Enter VLAN 1 in the database Exit VLAN database Enter VLAN 10 in the database Exit VLAN database Enter VLAN 4093 in the database Exit VLAN database Enter interface VLAN 10 configuration mode Define VLAN 10 IP address and subnet Exit interface configuration mode Enter interface VLAN 4093 configuration mode Def...

Page 11: ... on as soon as external power is applied 3 3 Serial Console Connection and Configuration Use the RJ45 to DB9 adapter provided with the platform to connect a non crossover Ethernet cable to establish a serial connection between PC and the RJ45 console port of the hub faceplate marking 1010 see label 2 in Figure 4 of the MS1300 Configure a serial console tool e g PuTTY with the correct COM port for ...

Page 12: ...em Connections You should now have access to The platform serial console used to access and configure management and payload components You can now proceed to section Switch Configuration Unboxing the platform Initial system connections Switch configuration Management configuration Payload access OS installation Performance assessment ...

Page 13: ...g the default credentials user admin and password admin Command Purpose MSH8900 Login Ctrl g Username admin Password admin Use HOTKEY to redirect serial console multiplexer to the switch CLI The prompt means the switch was reached The serial interface of the hub includes a multiplexing functionality that can establish a serial console link with each component of the platform through a series of ho...

Page 14: ...er VLAN 4093 interface configuration mode Configure VLAN 4093 IP address and subnet Exit Interface configuration mode Enter 1 3 uplink interface configuration mode Add VLAN 10 to the allowed hybrid mode VLAN list Exit the interface configuration mode Enter 1 7 24 interfaces MSP nodes configuration mode Add VLAN 10 to the allowed hybrid mode VLAN list Configure VLAN 10 as the native VLAN for 1 7 24...

Page 15: ... the MSP nodes s OS needs to be configured accordingly and this command line is not necessary Exit interface configuration mode Enter 1 25 management interface configuration mode Add VLAN 4093 to the allowed hybrid mode VLAN list Deconfigure VLAN 4093 as being the native VLAN Exit the interface configuration mode Enter the region name and revision Create MSTP instance 1 and assign VLAN 10 to it Cr...

Page 16: ...l 5 on Figure 4 4 8 Confirm Proper Networking Configuration Spanning Tree Confirm that the spanning tree configuration works properly by looking at the forwarding states of the uplinks connected to your networks Ethernet 1 3 payload data network and Ethernet 1 25 management network Both interfaces should be in forwarding state on MST instance 0 You should also look at the forwarding states of the ...

Page 17: ... 0 config if vlan end ping ip 192 168 10 254 PING server 192 168 10 254 56 bytes of data 64 bytes from 192 168 10 254 icmp_seq 0 time 0ms 64 bytes from 192 168 10 254 icmp_seq 1 time 0ms 64 bytes from 192 168 10 254 icmp_seq 2 time 0ms 64 bytes from 192 168 10 254 icmp_seq 3 time 0ms 64 bytes from 192 168 10 254 icmp_seq 4 time 0ms Sent 5 packets received 5 OK 0 bad Ping external management networ...

Page 18: ...d to manage the MS1300 platform perform firmware upgrades monitor system health and configure the platform more in depth 5 1 Set Up Access to the ShMC To access the ShMC CLI using the Ctrl g 0 command 1 2 Release both keys 3 0 4 Press the Enter key and release it Hint It is preferable to use the Ctrl key located on the left of the keyboard Log in the ShMC CLI using the default credentials user adm...

Page 19: ... Define static IP address Define netmask Define default gateway IP address Target BMC FRU0 of MSP node 1 Configure IP source to static Define static IP address Define netmask Define default gateway IP address Target BMC FRU0 of MSP node 2 Configure IP source to static Define static IP address Define netmask Define default gateway IP address Target BMC FRU0 of MSP node 3 Configure IP source to stat...

Page 20: ...on of the the ShMC Redirect bridging to the BMC of MSP node 1 Confirm configuration of the BMC of MSP node 1 Redirect bridging to the BMC of MSP node 2 Confirm configuration of the BMC of MSP node 2 Redirect bridging to the BMC of MSP node 3 Confirm configuration of the BMC of MSP node 3 Redirect bridging to the ShMC If you have not physically connected the MS1300 platform to the network as descri...

Page 21: ...vice providers and enterprise clients around the globe collaborate with Kontron and its ISV and channel partners to deploy new services with greater speed confidence and operational efficiency Our portfolio is a best of breed of OEM hardware and SYMKLOUD Open Infrastructure Platforms dedicated to the deployment of virtual services using software defined networks SDN and network functions virtualiz...

Reviews: