SR Wireless Network Engineer -- WMATA-002
Posting Title: SR Wireless Network Engineer
Specific Position Requirements
Is this a new requirement or is there an incumbent?
You must demonstrate an understanding and ability in the following Network Technologies:
• LAN Switching technologies including a detailed understanding of all Ethernet standards; Ethernet Layer 1 wiring speed and duplex, RJ-45 pinouts and CAT6 wiring, CSMA/CD, basic switch port configuration; VLAN configuration and management including VTP, ISL and 802.1q trunking.
• Detailed understanding of the spanning tree protocol to include PVST+, MST, Portfast, uplinkfast, backbonefast, root guard and BPDU guard.
• IPv4 addressing including IP address structure and subnetting, VLSM subnet allocation, CIDR, private addressing and NAT.
• IPv6 technologies, including a detailed understanding of IPv6 addressing and Address types, IPv6 neighbor discovery, neighbor and router advertisement and neighbor and router solicitation; unicast reverse path forwarding and IPv6 unicast routing protocols.
• IP Services including ARP, Proxy ARP, DHCP; HSRP, VRRP and GLBP, Network Time Protocol (NTP); SNMP; Syslog.
• Cisco Nexus technologies including an understanding of the 7018 switches, NX-OS Software, High Availability and other Nexus technologies.
• MPLS technologies, including provisioning MPLS routers via LDP, understanding of the LIB, LFIB as it relates to MPLS provision and path determination, tracking and troubleshooting,
• MPLS VPN implementation including a detailed understanding of MP-BGP, Route Distinguishers and route targets.
• EIGRP routing including configuration of EIGRP routers, authentication, route filtering, offset lists and troubleshooting stuck-in-active routes.
• OSPF routing including a detailed understanding of the OSPF database, configuring neighbors using different network types, the hello process, the OSPF path selection process, configuration of stubby areas, NSSA; configuration of OSPF costs and clearing of the OSPF process; OSPF route filtering, virtual link configurations and OSPF authentication.
• BGP routing including the configuration of iBGP and eBGP peers; BGP message types, neighbor states, injecting routes and prefixes into the BGP table; detailed understanding of BGP attributes;; understanding of the BGP path selection process.
• QoS technologies including congestion management and avoidance, software queues and Cisco switch hardware queues, CBWFQ and LLQ basic features and configuration, WRED operation, LAN switch congestion Management and avoidance with a particular emphasis on Cisco 3750 series, 6500 series and 7600 series switches; Shaping and policing concepts including shaping and policing terminology and the underlying mechanics of shaping and policing configuration and operation.
• IP Multicast technologies including a detailed understanding of the IP Multicast structure, distribution of IP multicast traffic with IGMP; IGMP v2 and version 3 implementation; IP Multicast routing with particular emphasis on Sparse mode routing protocols.
SOW Labor Category/Experience Level/WBS #
Sr. Network Engineer
Respond to Network Operational Issues
The ability to define, communicate, maintain ownership and resolve Network Problems
- You should be able to adequately define and narrow down the cause of the network operational issue in at least but not limited to the following:
- What business systems are impacted by the problem and in what fashion.
- Identify the end-to-end flow of data by IP address and type.
- The time periods associated with the issue
- It is expected that you utilize network troubleshooting tools and principles in the resolution of issues. The technical expertise associated with being able to troubleshoot and resolve network operational issues is critical. The use of IP commands, show commands, the NMS systems are all instrumental in defining issues and remediating them. It is expected that you know how to use these tools and can demonstrate your knowledge of them when troubleshooting.
- It is expected that you can document the problem definition and successfully communicate the issue in writing.
- The ability to communicate the definition of the problem to the client, NOC, colleagues and supervisors and to keep them updated. Your communications should be written in a fashion that adequately conveys the definition of the problem and what steps you are taking to address it. The updates should provide enough information for recipients to understand the network operational issue.
- For problems that are multi-faceted, and thus involve other groups (i.e., servers, desktops, cable runs...etc), the ability to maintain ownership of the "network" component of the issue. As "owner" of the issue it is your responsibility to see that the issue is remediated to its final conclusion in all aspects that involve NCS responsibilities. If the issue is clearly not an NCS responsibility, you must be able to define why it is not and to make sure that they client is aware of this fact by email. Within the scope of NCS responsibilities, it your responsibility to seek out resources if resolution of the issue is beyond your skill set and or means by informing your teammates and supervisor of this fact in a timely fashion.
- The ability to willingness to engage other groups and reach out to end users for problem definition and coordinated troubleshooting. You need to demonstrate your ability and willingness to communicate and work with other non-NCS groups in the resolution of issues by email, phone and in person when the situation warrants it. For example, many reported issues may have a component that involved IT security. It is expected that you can work with a group like this to define the problem, narrow down the issue and resolve it.
5. In the performance of this goal, deliver quality service, use every resource wisely and maintain and enhance Metro's image.
When assigned as the lead for a network project or provisioning request, design and implement network engineering technologies and configurations to solve problems needing network engineering solutions. Design and implement network electronics to solve customer network provisioning needs such as new end hosts and systems.
- It is expected in the delivery of this responsibility that you can write a network project document that defines a number of critical items as follows and to gather and report this information. The Network Project Document should:
- Define the problem or task that is the reason for the network technology solution.
- Define the end user requirements in a thorough and understandable manner.
- Define the scope of the work.
- Identify dates and expectations.
- Identify Point of contacts from both the NCS and customer side.
- Identify other non-NCS groups that are part of the solution and what their roles are.
- Identify any infrastructure issues or requirements that are critical for the completion of the work.
- Identify any other issues that are critical or must be overcome for the completion of the work.
- Include a network topology of the existing architecture.
- Include a network topology of the proposed architecture.
- Define the network electronics and materials such as cables and fiber needed to fulfill the solution.
- Define costs associated with the network electronics and materials needed to fulfill the solution.
- Identify the port counts needed to fulfill the solution.
- Identify the VLAN and IP subnets to be allocated.
- Include any voice requirements and backup plans for voice.
- Include a migration plan that details the steps needed to move from a before to an after scenario. This plan should provide enough detail that demonstrates how the solution can be implemented successfully.
- It is expected that you can develop a provisioning script and/or step by step procedure that details the implementation process and that this script is inclusive of all steps necessary to accomplish a successful implementation during one or more defined work windows. It is expected that you can lead the execution of the script that may or may not involve other individuals or groups during one or more defined work windows in a fashion that results in the successful completion of the work.
- When provisioning the network for network business systems and/or applications, it is expected that you can write documentation that accomplishes the following at a minimum:
- You should be able to identify the control plane elements that make up the business systems (control plane elements are defined as servers and applications that communication to with each other.)
- You should be able to identify the server to client and client to server or "data plane" elements.
- You should be able to identify systems by IP address and DNS host names.
- You should be able to articulate in writing how the control plane operates and how the data plane operates with the goal of understanding and identifying their requirements from the network.
- You should be able to develop Microsoft Visio topology maps that identify the interconnections between network elements both from a layer 2 perspective and a layer 3 perspective.
- It is expected that you have sufficient knowledge of the network technologies needed to implement the project and that you are able to demonstrate this knowledge in the development of the work script, presentation to others and implementation of the work.
- It is expected that you are able to submit change control requests that correspond to changes needed to implement the solution and to do so in a manner that adheres to the change control policy. It is important that you include in the CCB submission scripts that detail the work and that you understand the differences between operational and non-operational CCBs and can create them accordingly. The key goal is to execute your work in a manner that does not lead to unplanned network outages.
- It is expected that you can communicate with the client or end users by email, phone and in person to identify their requirements in a thorough manner.
- It is expected that you can work with other NCS and non-NCS groups that have responsibilities in the implementation and planning of the solution in a fashion that accomplishes the following goals:
- Defines roles and responsibilities.
- Defines a timeline for work coordinated work if necessary.
- Develops coordinated implementation scripts.
- It is expected that you can present your project or provisioning effort to your supervisor, teammates and customers in a fashion that is understandable and meets the goals that are defined in your network project document.
- It is expected that you can escalate to your supervisor issues that hinder the successful completion or progress towards completion of this project when you encounter them so that those obstacles can be removed and thus they do not impact the timeline associated with completing the work. Escalation should occur no later than one hour or close of business that day, whichever is sooner.
• It is expected that you can create a cost estimate for network electronic provisioning using the NCS cost estimate template that is accurate and presentable to our clients
NBS Enterprises creates competitive advantages. We isolate and overcome constraints to deliver performance value for all involved: you, your customer, and your employees. We break current market staffing trends with price-sensitive strategies solutions.
Our goal is to work in partnership with you, our client, become a trusted advisor and teammate to establish a relationship that provides you and your team with a competitive advantage at both the contract and at the task order levels. NBS' innovative 'Triangle' approach to staffing support provides you, your customer, and your future employee a risk mitigation solution that is second to none.
Thu, 11 May 2017 08:07:14 PDT