{"id":89,"date":"2026-08-06T18:49:25","date_gmt":"2026-08-06T18:49:25","guid":{"rendered":"https:\/\/mrnetwork.nl\/index.php\/basic-commands-on-alcatel-omniswitch-2\/"},"modified":"2026-08-06T20:00:07","modified_gmt":"2026-08-06T20:00:07","slug":"basic-commands-on-alcatel-omniswitch-2","status":"publish","type":"page","link":"https:\/\/mrnetwork.nl\/index.php\/basic-commands-on-alcatel-omniswitch-2\/","title":{"rendered":"Basic commands on Alcatel Omniswitch"},"content":{"rendered":"

Terug naar home<\/a><\/p>\n

Basic commands on Alcatel Omniswitch<\/h1>\n
Introduction<\/div>\n
This page is based on the notes I took when managing Alcatel Omniswitchs 6600, 6800 in 2007 and later 6850. The full documentation<\/a> can be found on Alcatel-Lucent website.<\/div>\n
Managing the configuration files<\/div>\n
Alcatel Omniswitchs can operate in two modes: working and certified (show running-directory to know in which mode the switch is). In working mode, the configuration can be modified, while it is no possible in certified mode (well, actually, it is). When booting, if working and certified configuration files are different, the switch will boot in certified mode. Configuration files are stored in certifed\/boot.cfg and working\/boot.cfg (they can be directly edited with “vi”). <\/p>\n
    \n
  • save running -> working: write memory<\/code><\/li>\n
  • save working -> certified: copy working certified [flash-synchro]<\/code>, flash-synchro<\/code> will synchronize the conf accross all slots<\/li>\n
  • save running even in certified mode: configuration snapshot all <file><\/code> Then move this file to working\/boot.cfg<\/li>\n
  • reboot in working mode without rollback: reload working no rollback-timeout<\/code><\/li>\n
  • view running configuration: show configuration snapshot [all|vlan|ip|...]<\/code> or write terminal<\/code><\/li>\n<\/ul>\n<\/div>\n
    When modifying the configuration, it can be useful to reload the switch in certified mode if a configuration error occur. It is possible to program the switch to reload a few minutes ahead in case you lose control: reload in <n><\/code> where n<\/code> is the number of minutes to wait before reloading. A reload can be canceled with reload cancel<\/code>. show reload<\/code> will show you when the switch will reboot.<\/div>\n
    Configure VLANs<\/div>\n
    A layer 2 VLAN is created with vlan <vlan_number> enable name \"vlan name\"<\/code> and removed with no vlan <vlan_number><\/code>. show vlan<\/code> lists all VLANs, show vlan <vlan_number><\/code> shows vlan <vlan_number> details.
    Depending on the microcode version (show microcode<\/code>), a layer 3 VLAN is created using: <\/p>\n
      \n
    • ip interface \"interface name\" vlan <vlan_number> address <address> mask <netmask><\/code><\/li>\n
    • vlan router \"interface name\" vlan <vlan_number> address <address> mask <netmask><\/code><\/li>\n<\/ul>\n

      and destroyed with: <\/p>\n

        \n
      • no ip interface \"interface name\"<\/code><\/li>\n
      • no vlan router \"interface name\"<\/code><\/li>\n<\/ul>\n

        Port association: <\/p>\n

          \n
        • To associate a port to a specific vlan: vlan <vlan_number> port default <slot>\/<port><\/code><\/li>\n
        • To list the ports: show vlan port<\/code><\/li>\n
        • To list the ports of a specified vlan: show vlan <vlan_number> port<\/code><\/li>\n
        • To show a port: show vlan port <slot>\/<port><\/code><\/li>\n

          802.1Q: <\/li>\n

        • To tag a port: vlan <vlan_number> 802.1Q <slot>\/<port> [<\"comment\">]<\/code><\/li>\n
        • To remove a tag: vlan <vlan_number> no 802.1Q <slot>\/<port><\/code><\/li>\n<\/ul>\n<\/div>\n
          Interfaces<\/div>\n
          Global status: Show interfaces status<\/code>
          Info about an interface (admin status, MAC, speed, duplex, errors, …): show interfaces [port|status|<slot>\/<port>|...]<\/code>
          Summary of interfaces errors: show interfaces counters errors<\/code>
          To clear counters: interfaces <slot>[\/port1-port2] no l2 statistics<\/code>
          To change an interface: interface <slot>\/<port> [speed <10_100_1000>|duplex <half_full>|autoneg <state>|flood rate <rate>]<\/code>
          To switch from autonegociation to 100FD, set<\/p>\n
            \n
          • autoneg off<\/li>\n
          • speed 100 and duplex full<\/li>\n<\/ul>\n

            If forced in 100FD while autoneg is on, the port will stay down
            To disable an interface: interface <slot>\/<port> admin down<\/code><\/div>\n

            Link Aggregation<\/div>\n
            Dynamic LAG (LACP)<\/div>\n
            lacp linkagg <id> size <size> admin state enable<\/code>
            lacp linkagg <id> actor admin key <key><\/code>
            lacp agg <slot\/port> actor admin key <key><\/code><\/div>\n
            Static LAG<\/div>\n
            static linkagg <id> size <size> admin state enable<\/code>
            static linkagg <id> name <name><\/code>
            static agg <slot\/port> agg num <id><\/code><\/div>\n
            Hardware<\/div>\n
            When stacking is operational, one switch is primary, one other secondary, the others idle. If the primary disappears, the secondary becomes primary and the first idle becomes secondary.
            Get info about the chassis: show chassis<\/code> and about the stack: show stack topology<\/code>. <\/div>\n
            To monitor the health of the system: show health all (cpu|memory)<\/code><\/div>\n
            Show CMM (Control Management Module \u2013 Alcatel ) information: show cmm<\/code><\/div>\n
            System<\/div>\n
            Uptime, date, name, contact, location: show system<\/code>
            To change: <\/p>\n
              \n
            • system name <\"name\"><\/code><\/li>\n
            • system contact <\"contact\"><\/code><\/li>\n
            • system location <\"location\"><\/code><\/li>\n<\/ul>\n<\/div>\n
              The default prompt is “->”. session prompt default \"sw1->\"<\/code> changes it to “sw1->”. You can get the other session parameters with show session config<\/code><\/div>\n
              When a command outputs to many lines on the screen, it is possible to use “more<\/code>” to see page by page. Use more<\/code> to activate the mode and more size <size><\/code> to set the number of lines shown. Cancel this mode with no more<\/code>.<\/div>\n
              To change the timeout of the telnet\/ssh sessions: session timeout cli <timeout><\/code><\/div>\n
              NTP<\/div>\n
              Set a server: ntp server <server_ip><\/code>. Even if the DNS is configured, you cannot specify a name for the NTP server. Then activate NTP: ntp client enable<\/code>.
              Get NTP info: <\/p>\n
                \n
              • show ntp client<\/code>: tells if NTP is on or off, when was the last updated, …<\/li>\n
              • show ntp server-list<\/code>: get the list of servers and with which server the swich is synchronized<\/li>\n<\/ul>\n<\/div>\n
                Logs<\/div>\n
                Show logging conf: show swlog<\/code>
                Get switch logs: <\/p>\n
                  \n
                • show log swlog<\/code>: get all logs<\/li>\n
                • show log swlog timestamp <mounth\/day\/year> <hour:minute><\/code>: only logs since the specified hour<\/li>\n
                • empty logs: swlog clear<\/code><\/li>\n<\/ul>\n

                  Enable syslog with: swlog output socket <syslog_server_ip><\/code><\/div>\n

                  STP<\/div>\n
                  STP can operates in two modes: flat and 1×1. In flat mode, there is only one instance for the whole switch whereas in 1×1 mode, there is one instance per VLAN (like pvst on Cisco switches or vstp on Juniper ones). I recommend the 1×1 mode if you do not want to go the MSTP way. Change STP mode: bridge mode (flat|1x1)<\/code><\/div>\n
                  Get STP conf: show spantree<\/code><\/div>\n
                  It is possible to deactivate STP on specified vlans\/ports : vlan <vlan_number> stp (enable|disable)<\/code> and bridge <vlan_number> <slot>\/<port> (enable|disable)<\/code><\/div>\n
                  Change STP algorithm: bridge protocol (802.1D|STP|RTSP)<\/code>. (In 2007), I did not manage to set rstp for all vlan as a global config, I had to set it vlan per vlan using: bridge 1x1 <vlan_number> protocol (802.1D|STP|RTSP)<\/code>.<\/div>\n
                  DNS<\/div>\n
                  \n
                    \n
                  • Name servers: ip name-server <IP1> <IP2><\/code><\/li>\n
                  • Domain name: ip domain-name <domain-name><\/code><\/li>\n
                  • Activate DNS client: ip domain-lookup<\/code><\/li>\n<\/ul>\n<\/div>\n
                    DHCP relay<\/div>\n
                    \n
                      \n
                    • ip service udp-relay<\/code><\/li>\n
                    • DHCP relay only for specified vlans: ip helper per-vlan only<\/code><\/li>\n
                    • DHCP server address: ip helper address <dhcp_server> vlan <vlan_number><\/code><\/li>\n
                    • Enable DHCP relay: ip udp relay BOOTP<\/code><\/li>\n<\/ul>\n<\/div>\n
                      Services<\/div>\n
                      Activate\/deactivate services: [no] ip service (ftp|ssh|telnet|http|secure-http|udp-relay|snmp|all)<\/code>. List of activated services: show ip service<\/code>.
                      For https: ip http ssl<\/code><\/div>\n
                      AAA<\/div>\n
                      Authentification can be local or made with a radius
                      To activate a service, the authentification have to be set: aaa authentification default \"local\"<\/code>, aaa authentification (console|ssh|ftp|802.1X|vlan|...) \"local\"<\/code><\/div>\n
                      ARP<\/div>\n
                      ARP table: show arp<\/code>
                      Mac Address table: show mac-address-table<\/code>
                      Add a static MAC\/IP entry: arp <IP> <MAC><\/code>, no arp <IP><\/code> to remove it.
                      Clear dynamic arp entries: clear arp-table<\/code>
                      To specify when an dynamic entry timeouts (default: 300seconds): mac-address-table aging-time <seconds> [vlan <vlan_number>]<\/code><\/div>\n
                      SNMP<\/div>\n
                      First, you have to create a user and give it the right to do SNMP: <\/p>\n
                        \n
                      • user <\"username\"> read-only (all|ip|interface|...) password <password><\/code><\/li>\n
                      • The only way I found to give the user SNMP capabilities is to use the web interface …, but you can desactivate it with user <\"username\"> no snmp<\/code><\/li>\n<\/ul>\n<\/div>\n
                        Then configure the snmp server: <\/p>\n
                          \n
                        • snmp security no security<\/code><\/li>\n
                        • Associate the community string with the user you created: snmp community map <\"community\"> user <\"username\"> on<\/code><\/li>\n<\/ul>\n
                            \n
                          • To configure the SNMP trap server: snmp station <server_ip> [<port>] <\"user\"> (v1|v2c|v3) enable<\/code><\/li>\n
                          • snmp authentification trap (enable|disable)<\/code><\/li>\n<\/ul>\n
                              \n
                            • To filter the traps sent by the switch: snmp trap filter <server_ip> <filter_code><\/code><\/li>\n<\/ul>\n<\/div>\n
                              Port mirroring<\/div>\n
                              Port mirroring works 12 ports by 12 ports. It is possible to configure multiple sources for one session and thus see the traffic of multiple ports in one output. <\/p>\n
                                \n
                              • show port mirroring status<\/code><\/li>\n
                              • port mirroring <session> source <slot>\/<port> destination <slot>\/<port> enable<\/code><\/li>\n
                              • no port mirroring <session><\/code><\/li>\n<\/ul>\n<\/div>\n
                                POE<\/div>\n
                                By default, the POE is disabled on all ports.
                                To enable the POE on a given port: lanpower start <slot>\/<port><\/code>
                                To enable it on the whole slot: lanpower start <slot><\/code><\/div>\n
                                To stop the POE, use the symmetric commande lanpower stop (<slot>\/<port>|<slot>)<\/code><\/div>\n
                                Show the POE configuration: show lanpower <slot><\/code><\/div>\n
                                To limit the power available for a given port: lanpower <slot>\/<port> power <milliwatts><\/code>
                                To limit the power available for a slot: lanpower <slot> maxpower <watts><\/code><\/div>\n
                                A power of 230W is enough for a full slot equipped with IP Phones (note: TBC).
                                It has been noticed that a switch may prove instable with POE if too many equipments are connected and its PSU is not enough powerfull.<\/div>\n
                                QOS & ACL<\/div>\n
                                In AOS, ACL and QoS are configured in the same “qos” section.
                                Apply QoS when modified:qos apply<\/code>
                                Disable QoS (useful for troubleshooting):qos disable<\/code><\/div>\n
                                By default, QOS is not trusted in access ports and all tags are set to 0. It is trusted on trunked ports. To trust everywhere:qos trust ports<\/code>
                                To trust on one given port:qos port <slot>\/<port> trusted<\/code><\/div>\n
                                The rules are a combinaison of the following elements:<\/p>\n
                                  \n
                                • policy network : define subnets<\/li>\n
                                • policy condition : define conditions (from subnet1 to subnet2, …)<\/li>\n
                                • policy action : define actions (permit, deny, …)<\/li>\n
                                • policy rule : apply action to condition (if X then Y)<\/li>\n<\/ul>\n

                                  The syntax for the different blocks is the following:
                                  policy network group <gp_name> <subnet1> mask <mask1> <subnet2> mask <mask2> ...<\/code>
                                  policy condition <c_name> source network group <gp_name1> destination group <gp_name2><\/code>
                                  policy action <a_name> disposition <action><\/code>
                                  policy rule <r_name> [disable] precedence <p> condition <c_name> action <a_name><\/code>, where precedence is the order rules can be applied<\/div>\n

                                  \n
                                  \n

                                  TERMINAL As an example:<\/p>\n

                                    \n
                                  • policy network group VoIP 192.168.1.0 mask 255.255.255.0 192.168.11.0 mask 255.255.254.0 <\/li>\n
                                  • policy network group Data 172.16.0.0 mask 255.255.255.0 <\/li>\n
                                  • <\/li>\n
                                  • policy condition “VoIP-VoIP” source network group VoIP destination network group VoIP <\/li>\n
                                  • policy condition “VoIP-Data” source network group VoIP destination network group Data <\/li>\n
                                  • policy condition “Data-Data” source network group Data destination network group Data <\/li>\n
                                  • policy condition “Other” source ip any destination ip any <\/li>\n
                                  • <\/li>\n
                                  • policy action Deny disposition deny <\/li>\n
                                  • policy action Permit <\/li>\n
                                  • <\/li>\n
                                  • policy rule “Allow VoIP-VoIP” precedence 200 condition “VoIP-VoIP” action Permit <\/li>\n
                                  • policy rule “Allow VoIP-Data” disable precedence 200 condition “VoIP-Data” action Permit <\/li>\n
                                  • policy rule “Allow Data-Data” precedence 200 condition “Data-Data” action Permit <\/li>\n
                                  • policy rule “Deny Other” precedence 200 condition “Other” action Deny <\/li>\n
                                  • <\/li>\n
                                  • qos port 1\/2 trusted <\/li>\n
                                  • qos port 1\/3 trusted <\/li>\n
                                  • qos apply <\/li>\n<\/ul>\n<\/div>\n<\/div>\n
                                    802.1X<\/div>\n
                                    \n
                                    aaa radius-server \"radius_srv1\" host <IP Addr> key <auth_key> retransmit 3 timeout 2 auth-port 1812 acct-port 1813aaa radius-server \"radius_srv2\" host <IP Addr> key <auth_key> retransmit 3 timeout 2 auth-port 1812 acct-port 1813# Use the radius for vlan assignementaaa authentication vlan single-mode \"radius_srv1\" \"radius_srv2\"# use the internal database for authent to the local servicesaaa authentication default \"local\"aaa authentication console \"local\"aaa authentication ftp \"local\"aaa authentication snmp \"local\"# 801.1X authentication serversaaa authentication 802.1x radius_srv1 radius_srv2# MAC base authentication servers (used for devices that can't do 802.1X like IP-Phones)aaa authentication mac radius_srv1 radius_srv2AVLAN:# Authentication portal in the switch. By default, last IP of the subnet.avlan auth-ip <vlan-ID> <IP address, in same VLAN, different of switch IP address>VLAN definitionvlan 5 enable name \"VoIP\"vlan 10 enable name \"Data\"vlan 10 authentication enableconfiguration of interface 1\/3vlan 10 port default 1\/3# enable dynamic vlan assignemtvlan port mobile 1\/3# enable 802.1X vlan port 1\/3 802.1x enable# 802.1X# - direction both => control on inbound + outbound traffic# - port-control auto => port initially in unauthorized state, and put in \"authorized mode\" automatically by the switch upon the exchanged between the switch and the end station# - quiet-period 60 => reject the 802.1X authentications during 60s after an authentication failure# - server-timeout 30 => superseded by the aaa radius-server ... timeout# - re-authperiod 3600 => 3600s=1h before re-authent is required# - no reauthentication => disables the reauthent802.1x 1\/3 direction both port-control auto quiet-period 60 tx-period 30 supp-timeout 30 server-timeout 30 max-req 2 re-authperiod 3600 no reauthentication# length of a captive portal session802.1x 1\/3 captive-portal session-limit 12 retry-count 3# poll the end device 2 times before stating it is not 802.1X compliant802.1x 1\/3 supp-polling retry 2# if authentication is successful but returns no VLAN ID (\"pass\"), use default vlan for the supplicant else (\"fail\"), block the port802.1x 1\/3 supplicant policy authentication pass group-mobility default-vlan fail block#idem for non supplicant (not 802.1X) devices - authentication by MAC address with a Radius802.1x 1\/3 non-supplicant policy authentication pass group-mobility block fail block# used by supplicant and non supplicant when \"captive-portal\" is used in the \"802.1x supplicant policy\" or \"802.1x non-supplicant policy\"802.1x 1\/3 captive-portal policy authentication pass default-vlan fail block<\/pre>\n<\/div>\n","protected":false},"excerpt":{"rendered":"
                                    Terug naar home Basic commands on Alcatel Omniswitch Introduction This page is based on the notes I took when managing Alcatel Omniswitchs 6600, 6800 in 2007 and later 6850. The full documentation can be found on Alcatel-Lucent website. Managing the configuration files Alcatel Omniswitchs can operate in two modes: working and certified (show running-directory to […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"blank","meta":{"footnotes":""},"class_list":["post-89","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/mrnetwork.nl\/index.php\/wp-json\/wp\/v2\/pages\/89","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mrnetwork.nl\/index.php\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/mrnetwork.nl\/index.php\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/mrnetwork.nl\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mrnetwork.nl\/index.php\/wp-json\/wp\/v2\/comments?post=89"}],"version-history":[{"count":5,"href":"https:\/\/mrnetwork.nl\/index.php\/wp-json\/wp\/v2\/pages\/89\/revisions"}],"predecessor-version":[{"id":191,"href":"https:\/\/mrnetwork.nl\/index.php\/wp-json\/wp\/v2\/pages\/89\/revisions\/191"}],"wp:attachment":[{"href":"https:\/\/mrnetwork.nl\/index.php\/wp-json\/wp\/v2\/media?parent=89"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}