110 likes | 222 Vues
This talk by Hans Nilsson discusses the management of local node resources in the AXC105 Fibre Switch, focusing on the integration of various components such as Ethernet switches, network processors, and the underlying software stack including Linux and Erlang. Key topics include the operational architecture, the role of SNMP and CLI for user interaction, and the management of resources like Ethernet ports, bandwidth limitations, and alarms. Nilsson shares insights on development challenges and the importance of flexible system architecture in network management.
E N D
The AXC105 Fibre Switch Hans Nilsson hans@erix.ericsson.se
This talk: the local node Management The access system ISPs
Photos Rack installation Mounted on a wall with fibres to the users
The local node is basically an Ethernet Switch • Network processor • Assembler • PowerPC • Linux • Erlang/OTP (35 k lines) • C (10 k lines) • Hardware • Another story…
Ethernet Frames Ethernet Frames Network Processor What does what SNMP Telnet SSH … PowerPC • Erlang • C • Linux Tables, registers
In Erlang: Resources • Everything manageable is a resource: • Ethernet Port • Bandwidth limitation • CPU • LED • Clock • Alarm • …
Models HW and the function: • Ethernet port • Network processor • Vlan • Mezzanine board • Main board • Bandwidth limitation • … • User- and machine interfaces: • SNMP • CLI (Command Line Interface) over telnet • … • Independent of HW and function: • Error logger • Trace logger • Database • Alarm • … Generic Interface Resources Generic Resources Function Specific Resources ELN Resource System – example of Resources
Generic Resources Generic Interface Resources Function Specific Resources SNMP Telnet/cli The Resource System etc Generic Resource System Development Support Application & HW Independent Parts HW_LIB NP_LIB Application Core Linux Drivers NP-SW HW Dependencies Hardware CPU NP
Resources • The Resource System: • coordinates actions performed by the different resources • supervises the resources • provides an API • A Resource: • is started by the Resource System • performs actions at start-up (initiates registers, load code …) • execute orders sent to the resource (set, get, reset, call, check …) • Provides configuration data to the CLI (Commands)
Good Linux: Much available out there Many experts Erlang: High level Very short development time Network Processor Flexible Bad Linux: Not completely perfect Allergic reactions … Erlang: Nothing bad Allergic reactions … Network Processor Expensive Allergic reactions … Experiences