Network Administrator

You are the junior network tech. The battalion has NIPR, SIPR, and VoIP because someone ran the cable, mounted the switch, and did not typo the VLAN assignment at 0200 — that someone is you.

You arrive at your communications unit from the Marine Corps Communication-Electronics School (MCCES) at Twentynine Palms with a working knowledge of IP addressing, Cisco IOS, and the USMC network architecture stack that the section chief will either confirm or correct inside the first week. In garrison you rack and cable equipment in the server room, provision user accounts in Active Directory, help the senior Marines run patch management cycles, and pull the working parties — armory guard, barracks duty, motorpool — that hold the section alive between field ops. In the field you stand up the local area network at the forward command post: switches, routers, IP phones, NIPR/SIPR separation at the firewall boundary, and the HBSS endpoint agent on every device that touches the Marine Corps Enterprise Network. You log everything in the trouble-ticket system, and the section chief reads what you wrote.

• 01Configure a managed Cisco switch — VLANs, trunking, spanning tree, port security — from the IOS command line without a cheat sheet, to DISA STIG baseline.
• 02Maintain NIPR/SIPR separation at every network boundary: separate switch infrastructure, separate cabling, separate cable labels, physically verified before power-up.
• 03Install and check the HBSS (Host Based Security System) endpoint agent on Windows hosts and report compliance status to the ISSM in the format the unit uses.
• 04Provision and disable Active Directory user accounts and group memberships following the unit's access-control SOP — no accounts left open after PCS or EAS.
• 05Run an IP addressing scheme for a small LAN from a given subnet and document the assignments in the network diagram the section maintains.
• 06Perform operator-level preventive maintenance on switches, routers, and patch panels and complete the maintenance log before returning gear to the rack.

• —NAVMC 3500.44 — Communications Training and Readiness Manual (the individual and collective tasks for 06-series network admins you are evaluated against).
• —DISA STIGs (Security Technical Implementation Guides) — the mandatory configuration baseline for every device on the MCEN; your work is audited against these.
• —DoDD 8500.01 — Cybersecurity (the DoD-level policy that defines why NIPR/SIPR separation is non-negotiable and not a suggestion).
• —MCO P2000.11 — Marine Corps COMSEC policy (crypto key material on the network is your responsibility alongside the COMSEC custodian).
• —MCO 6100.13 — Marine Corps Physical Fitness, Body Composition, and Military Appearance (your PFT/CFT standard — every 0631 is still a Marine).

• —1st-Class PFT and CFT — the network section humps its gear through the same mud as the infantry; the fitness standard is operationally real.
• —Annual Rifle Qualification: Expert is the floor. Every 0631 is a Marine first.
• —Zero STIG-failed findings on any device you configured for network deployment — one open Critical or High finding on the ACAS scan delays the mission.
• —MCMAP Gray Belt before LCpl; Green Belt before you sit a Corporals Course board.
• —Pass the NAVMC 3500.44 individual network tasks at the company-level evaluation — switch configuration, VLAN assignment, account provisioning — without re-runs.

• —Creating a bridging loop by connecting two switches without checking spanning tree first. A broadcast storm at the forward command post kills the commander's NIPR and takes down the VoIP phones before anyone knows what happened.
• —Leaving the default admin password on a switch or router. The ACAS scan finds it, the ISSM finds the scan, and your section chief explains it to the S6.
• —Cross-connecting a NIPR cable to a SIPR port. The separation exists because classified traffic on an unclassified network is a spillage incident — the IG investigation starts the moment someone reports it.
• —Closing trouble tickets without verifying the fix. A ticket marked "resolved" that the user reopens six hours later makes the trouble-ticket system useless and the section chief's next review painful.
• —Posting OPSEC-relevant information about network architecture, IP ranges, or communications infrastructure on social media. The S2 runs sweeps and the ISSM is cc'd on the report.

The good junior network tech is the Marine the section chief sends to cable and configure the forward command post LAN and trusts to come back with a documented network diagram, clean HBSS compliance, and no open STIG findings on the ACAS scan. By month nine he is provisioning accounts without supervision; by the LCpl-to-Cpl evaluation cycle the section knows who is going to the Corporals Course slate and who is becoming the switch SME.

You are the network NCO. The junior operators wire the room; you are the one who tells them which VLAN the voice traffic lives on and then checks the trunk before the S3 walks in to brief.

You supervise two to four junior network techs and own the LAN from the IDF to the user's desk — VLAN design, switch configuration, firewall rules, VoIP provisioning, and the trouble-ticket queue that the section chief reviews every Monday. You run PCC/PCIs before field operations, brief the team on the network plan, and write proficiency and conduct marks that feed your Marines' composite scores. You are also the first NCO the section chief calls when the HBSS console shows an unmanaged endpoint or the ACAS scan returns a new Critical finding — and you are expected to have a remediation plan before you report back. In garrison you mentor the junior techs through NAVMC 3500.44 individual tasks, sign their CARPs, and track the Corporals Course slot that is always closer than they think.

• 01Brief a network stand-up tasking to a two-to-four person team — IP addressing plan, VLAN assignments, switch roles, firewall ACL requirements, NIPR/SIPR boundary verification — from the communications plan without the section chief in the room.
• 02Run a PCC/PCI for a network field kit — switches, routers, cables, power, labeling — as a real inspection with consequences, not a head-nod ritual.
• 03Analyze an ACAS vulnerability scan, triage findings by STIG severity category (CAT I / II / III), and build a remediation priority list the section chief can brief to the S6.
• 04Configure a perimeter firewall ACL for a forward command post LAN — required traffic, denied traffic, logging enabled — without leaving an overly permissive any/any rule hiding in the policy.
• 05Provision, configure, and troubleshoot VoIP phones on the garrison and tactical LAN — VLAN tagging, QoS marking, DHCP scope — in the time the communications order allows.
• 06Train junior techs on NAVMC 3500.44 individual network tasks, evaluate them against the task standard, and sign the CARP.

• —NAVMC 3500.44 — Communications T&R Manual (collective and individual tasks for network section NCOs; you run training against this and sign your team's CARPs).
• —DISA STIGs — you own the remediation cycle on the findings your team generates; the ACAS report lands on your section chief's desk with your name on the open findings.
• —DoDD 8500.01 — Cybersecurity; the ISSM cites this when the S6 asks why an exception to policy requires command-level signature.
• —MCO 1610.7 — Performance Evaluation System (you write proficiency and conduct marks now; the FitRep is coming).
• —MCO 1400.32 — Marine Corps Promotion Manual (composite scores and cutting scores for 0631 to Sgt).

• —Corporals Course graduate — required and gated; the Sgt board does not wait for your schedule.
• —Green Belt MCMAP minimum; Brown Belt is what the section chief notes on the FitRep going to the Sgt board.
• —1st-Class PFT and CFT — your team runs the same hump schedule you do.
• —Composite score tracked monthly in TFRS; pull the current cutting score for 0631 to Sgt before asking the section chief where you stand.
• —Zero open CAT I (Critical) STIG findings on any network segment your team owns through the full duty cycle.

• —Deploying a switch with factory defaults because "we'll harden it after the field op." The ACAS scan runs the night you deploy, the ISSM reads the output the next morning, and the section chief finds out before you brief it.
• —Assigning the same IP address to two devices on the same segment. An IP conflict that knocks the battalion commander's workstation offline at 0600 the morning of a brief is a memorable way to introduce yourself to the S6.
• —Leaving an unmanaged endpoint — a personal laptop, a government device someone brought from home — connected to the MCEN port. One unmanaged device with a zero-day on it is a reportable cyber incident.
• —Approving a firewall rule change verbally without a written change request. The ISSM change-management process exists because an undocumented rule change that breaks connectivity has no rollback plan.
• —Treating the NIPR/SIPR boundary verification as a "we know it's right" assumption. The physical verification — separate cables, separate labels, separate switch stacks, confirmed by two people — happens before every field operation, not after.

The good Cpl 0631 is the network NCO the section chief sends to stand up the battalion forward command post LAN with a team of two junior techs and trusts to return with a documented network diagram, zero open CAT I findings on the ACAS scan, and all VoIP phones registered before the first staff brief. His junior techs are training on IOS command-line tasks during garrison weeks, and the platoon sergeant has already passed his name to the company gunny for the Sgt board.

You are the network section chief. The battalion's NIPR, SIPR, and VoIP runs on the architecture your section built and the standards your Marines hold — and the S6 holds you personally accountable for both.

You run the network section — five to fifteen Marines across multiple teams, the full inventory of switches, routers, firewalls, and VoIP infrastructure the battalion operates on the MCEN. You translate the battalion communications plan into a network support order, manage the HBSS and ACAS compliance cycle for every device your section owns, write FitReps on your Cpls under MCO 1610.7, and brief the battalion S6 on network readiness at every BUB. You are the first call when the battalion commander's VTC fails and the S3 wants a restoration time before the next meeting — and you are expected to have a working hypothesis and a restoration plan before you key up. In garrison you build the section training schedule against NAVMC 3500.44 collective tasks, manage the equipment maintenance and TMDE calibration cycle, and mentor your Cpls through Sergeants Course prep and the SSgt board pipeline.

• 01Translate a battalion communications plan into a network support order — IP addressing scheme, VLAN architecture, firewall policy, VoIP provisioning plan, NIPR/SIPR boundary architecture, HBSS deployment plan — that the Cpls can execute without a follow-up brief.
• 02Manage the HBSS console for the section's device inventory — endpoint agent compliance, policy exceptions documented, unmanaged assets resolved — and brief compliance percentage to the ISSM weekly.
• 03Run the ACAS scan cycle for the section's network segments, triage the output by CAT I/II/III, brief remediation status to the S6, and close the finding with a documented fix rather than a scheduled exception.
• 04Write FitReps on two to three Cpls per cycle under MCO 1610.7 — observed behavior, action-result-impact, defensible relative value — that the reporting senior can defend at the battalion FitRep review.
• 05Coordinate with the regiment or communications battalion S6 for MCEN access authorization, IP address space allocation, and COMSEC key distribution before every major exercise or deployment.
• 06Mentor two Cpls through Sergeants Course prep and the SSgt board pipeline — composite score management, FitRep literacy, section-chief technical depth.

• —NAVMC 3500.44 — Communications T&R Manual (section-chief level network collective tasks; the S6 evaluates your section against this).
• —DISA STIGs — you own the remediation program for the section; every open CAT I finding is a signed POA&M with your name on it.
• —DoDD 8500.01 — Cybersecurity; the policy framework that defines the ISSM's authority over your network segment.
• —MCO P2000.11 — COMSEC; crypto key material on the network backbone is your section's responsibility alongside the COMSEC custodian.
• —MCO 1610.7 — Performance Evaluation System (you write FitReps for your Cpls now).
• —MCO 1400.32 — Marine Corps Promotion Manual (SSgt board mechanics, composite scores, 0631 MOS roadmap).

• —Sergeants Course graduate — required and gated.
• —Brown Belt MCMAP minimum; Black Belt is what the company gunny notes going to the SSgt board.
• —Network segment ACAS compliance at or above the ISSM-set threshold for CAT I closure — open Critical findings on your section's segments at inspection time end the conversation fast.
• —All network equipment operational or deadlined with a parts-on-order report delivered to the S6 before the exercise start line.
• —Composite score tracked monthly; pull the current MARADMIN cutting score for 0631 to SSgt before asking the section chief where you stand.

• —Signing off a firewall policy change without reviewing the rule base for shadowed or overly permissive rules. One any/any rule hiding in a 200-line ACL is the finding the ISSM walks up to the S6 on inspection day.
• —Verbal HBSS exception approvals. Every unmanaged endpoint or policy exception is documented in writing with a risk acceptance signed by the ISSM — verbal agreements evaporate when the IG arrives.
• —Letting a switch firmware update slip past its IAVA (Information Assurance Vulnerability Alert) window. An IAVA past due on a network switch in your section is a reportable compliance failure that goes up to the regiment S6 automatically.
• —Running a network configuration change without testing the rollback procedure first. A change that breaks connectivity in the battalion command post at 1800 and has no documented rollback is your problem until 0600.
• —Hiding a network outage from the S6 to avoid the conversation. The S6 finds out from the battalion S3, who found out from the commander, who found out because his email stopped working — and that is the last network outage the section chief manages from this chair.

The good Sgt 0631 is the section chief the S6 can hand a battalion communications order on Monday and trust that the NIPR, SIPR, and VoIP are up, HBSS compliance is current, and the ACAS remediation POA&M is briefable before the regimental BUB on Friday. His Cpls are Sergeants Course-ready, the switch inventory is accounted for, and the battalion commander's VTC has never failed on his section's fault.

You are the senior network SNCO. The MAGTF's garrison and tactical network architecture runs through your planning, your section chiefs report to you, and the general officer's command post runs on the infrastructure you specified.

You run the network platoon or serve as the senior network SNCO in a communications company — 15 to 30 Marines across multiple sections, the full range of switches, routers, firewalls, HBSS consoles, and ACAS infrastructure the unit operates on the MCEN. You build the network support plan for major exercises and deployments, write three to four FitReps per cycle on your section chiefs and senior Cpls, brief the regimental S6 and the communications officer on network readiness at the combined-arms rehearsal, and manage the ISSM relationship for the platoon's device inventory. You mentor two to three Sgts toward Career Course graduation and GySgt-board readiness, coordinate IP address space and MCEN access authorization with the communications battalion, and run the HBSS and ACAS compliance program at the platoon level. The SSgt-to-GySgt board is FitRep-driven — one weak cycle changes the timeline more than most SSgts realize.

• 01Build a network support plan for a battalion-level or MEU exercise or deployment — IP addressing scheme, VLAN architecture, NIPR/SIPR boundary design, HBSS deployment, ACAS scan schedule, VoIP provisioning — that the regimental S6 can brief without rewrites.
• 02Write three to four FitReps per cycle under MCO 1610.7 that the reporting senior can defend at the battalion FitRep review.
• 03Coordinate MCEN access authorization, IP address space allocation, and STIG baseline requirements with the communications battalion and the regimental ISSM for every major operation.
• 04Run the HBSS and ACAS compliance program at the platoon level — console health, policy exceptions documented, CAT I findings closed on POA&M timelines — and brief status to the regimental ISSM.
• 05Mentor two to three Sgts into Career Course graduates and SSgt-board-ready candidates — FitRep literacy, composite score management, section-chief technical depth.
• 06Run a platoon equipment inspection and TMDE calibration cycle for the full network device inventory and deliver the deadline report to the S6 before the window closes.

• —NAVMC 3500.44 — Communications T&R Manual (platoon-level network collective standards you build training against).
• —DISA STIGs — you own the compliance program for the platoon's device inventory and the POA&M tracking that goes up to the regimental ISSM.
• —DoDD 8500.01 — Cybersecurity; the policy basis the ISSM cites in every exception to policy request you sign.
• —MCO 1610.7 — Performance Evaluation System (FitRep policy for the Sgts and Cpls you rate).
• —MCO 1400.32 — Marine Corps Promotion Manual (SSgt-to-GySgt board mechanics, FitRep relative value impact).
• —MCO P2000.11 — COMSEC; crypto key material on the network backbone remains your section's responsibility at the platoon level.

• —Career Course (resident or distance) completed; SNCO Academy resident slot slated when the GySgt board approaches.
• —Black Belt MCMAP — the platoon expects the senior SNCO to be a senior instructor in the company.
• —HBSS compliance above the regimental ISSM-set threshold across the full platoon device inventory.
• —Zero open CAT I STIG findings on any network segment owned by the platoon at inspection time.
• —FitRep relative value above battalion average — one weak cycle on the SSgt-to-GySgt board moves the timeline by years.

• —Delegating the ACAS scan schedule to a section chief without a back-brief and a compliance report. The regimental ISSM does not accept "my section chief said it was clean" — the signed compliance dashboard is the answer.
• —Writing a FitRep as a wish list instead of an evaluation. The reporting senior who defends an inflated Sgt at the battalion FitRep board remembers the SSgt who wrote it.
• —Allowing a section chief to manage the IP address space by memory instead of by a maintained network diagram with version control. The marine who inherits the network after a PCS rotation needs the diagram, not the tribal knowledge.
• —Skipping the pre-exercise HBSS compliance baseline. When an unmanaged endpoint shows up on the network during the exercise, the ISSM's first question is whether you had a baseline — blank console history means you start debugging from zero.
• —Hiding a network segment with persistent STIG findings from the regimental ISSM to avoid the conversation. The ISSM finds out at the inspection from the automated scan, not from you, and that is the last conversation you have as the platoon sergeant.

The good SSgt 0631 is the platoon sergeant the S6 can walk out of a pre-deployment brief and trust that the network nodes will be up on the operational timeline, the ACAS compliance dashboard will pass the ISSM review, and the section chiefs can brief their segment assignments without him in the room. His Sgts are Career Course-ready, and the regimental S6 knows his name before the battalion does.

You are the network chief or the S-6 operations chief. The regimental or MEF MCEN architecture runs through your planning, your section chiefs report to you, and the commanding general's command post network is the one you designed.

You run the network section at the regimental or MEF support group level — 25 to 50 Marines across multiple sections, the full range of network infrastructure in the unit inventory, and the HBSS/ACAS compliance program that the regimental ISSM validates every quarter. You write three to five SSgt FitReps per cycle that feed the GySgt board, brief the regimental S6 and the MEF G6 on network readiness at the combined-arms rehearsal, manage the ISSM relationship for the full section, and coordinate IP address space and MCEN access authorization with the communications battalion and MARFORCYBER for every major operation. You mentor two or three SSgts toward Career Course graduation and GySgt-board readiness, and you are the SNCO the communications officer calls when the MEF commander's network fails and he needs to know within 60 seconds what the fault is and when it will be restored.

• 01Build and defend the network support plan for a regimental or MEF operation — IP addressing architecture, VLAN design, NIPR/SIPR boundary architecture, HBSS deployment, ACAS compliance schedule, VoIP and video teleconference infrastructure — in a format the communications officer can brief at the combined-arms rehearsal.
• 02Write three to five SSgt FitReps per cycle under MCO 1610.7 that the reporting senior can defend at the regimental FitRep board.
• 03Coordinate MCEN access authorization, IP address space, and STIG baseline requirements with the communications battalion, the regimental ISSM, and MARFORCYBER for every major operation, with a coordination record the communications officer can show the MEF G6.
• 04Run the HBSS and ACAS compliance program for the full section — console health, CAT I POA&M timelines, policy exception documentation — and brief status to the regimental ISSM and the MEF G6 on the cycle the ISSM sets.
• 05Mentor two to three SSgts into Career Course graduates and GySgt-board-ready candidates — honest reads on who is troop-leadership track and who is the cyber/network SME the MMPB needs on the MEF G6 staff.
• 06Brief the regimental SgtMaj and the communications officer honestly on section morale, gear readiness, retention trends, and the second-order effects of deployment or training tempo on network Marines.

• —NAVMC 3500.44 — Communications T&R (regimental / MEF collective network standards; the communications officer evaluates your section against this).
• —DISA STIGs — you own the section-level compliance program; every open CAT I finding on a segment in your section is a signed POA&M with your name on it.
• —DoDD 8500.01 — Cybersecurity; the ISSM cites the Authorizing Official chain under this directive when an exception to policy requires general officer signature.
• —MCO 1610.7 — Performance Evaluation System (FitRep mechanics you now teach to your SSgts).
• —MCO 1400.32 — Marine Corps Promotion Manual (GySgt-to-MSgt / 1stSgt board mechanics and MOS roadmap).
• —MCO 5354.1 / MCO 1000.9 — SAPR and Equal Opportunity policy (you enforce these, the IG validates them).

• —SNCO Academy Advanced Course (Career Course) graduate; SNCO Academy Senior Course slated as the MSgt board approaches.
• —Black Belt Instructor (MCMAP) — you are a senior instructor at the regimental or MEF level.
• —Section HBSS compliance above the regimental ISSM-set threshold and zero open CAT I findings on any network segment during every inspection cycle.
• —FitRep profile that the senior reporting official can defend at the MSgt / 1stSgt board — relative value, attribute rationale, all aligned.
• —1st-Class PFT and CFT; the formation watches the GySgt's scores more carefully than anyone's except the 1stSgt's.

• —Allowing an SSgt to coordinate MCEN access changes independently without a back-brief and a coordination record. An unauthorized change to the MCEN routing table at the regiment level generates an incident report that reaches MARFORCYBER; the GySgt who delegated without documentation absorbs it.
• —Confusing being tight with the S6 with being aligned with the S6. The MEF needs you to push back on a network architecture you know is under-resourced — in his office, with the door closed — not to agree with a plan you know will fail during the exercise.
• —Carrying a peer-SNCO feud into the regimental network section. The BSgtMaj notices, the FitRep board notices, and the MSgt slate writes itself without your name.
• —Allowing a section chief to manage the IP address space and network diagram by memory. The marine who takes the section after a PCS has the diagram or starts from scratch — and the S6 finds out which one it is during the next regimental BUB.
• —Stopping personal PT because you are too senior. Marines stop respecting the chevrons when the body stops carrying them, and the 1st-Class PFT is still the bar.

The good GySgt 0631 is the network chief the MEF G6 can brief a full deployment communications plan to on Monday and trust that the NIPR, SIPR, and VoIP are up, the ACAS compliance dashboard is green, and the SSgts can brief their segment assignments without him in the room. His section chiefs are getting GySgt-board-ready, his Marines re-enlist because of the school slots and the technical credibility of the section, and the regimental SgtMaj is already mentioning his name for the MSgt or 1stSgt slate before the board convenes.

You are the standard-bearer for the network formation. The split between the 1stSgt / SgtMaj troop-leadership track and the MSgt / MGySgt occupational-SME track is the career decision that defines your final decade — and the 0631 community is small enough that both paths are visible to everyone in it.

As 1stSgt you run the communications company or detachment — 100 to 180 Marines, the company office, the section chiefs, and the boundary between what the commanding officer needs and what the company can actually deliver on the network. As MSgt you are the senior network SME — regimental network chief, MEF G6 section SNCO, MOS roadmap owner, or the HQMC C4/cyber staff SNCO who shapes the next generation of 0631 GySgts. As SgtMaj you advise the battalion, regimental, or MEF commander on every enlisted decision in the communications community and you set the standard for how network Marines are developed across an entire echelon. As MGySgt you are the occupational pinnacle of the field, the Marine HQMC calls when the 06-series T&R program or the 0631 MOS roadmap needs rewriting. You write fewer FitReps but the ones you write determine the next GySgt, 1stSgt, and MSgt slates.

• 01Run a 1stSgt's call that handles accountability, sick call, discipline, family readiness, training calendar, and HBSS/ACAS compliance status in 30 minutes flat — without the GySgts running to fill silence.
• 02Build a communications company quarterly training schedule with the CO and the operations chief that survives the battalion BUB without losing the network sections.
• 03Mentor four GySgts and the senior SSgts as the next 1stSgt / MSgt cohort — honest reads on who is troop-leadership track and who is the cyber/network SME the MMPB needs on the MEF G6 or MARFORCYBER staff.
• 04Walk the network sections during a battalion or regimental MCCRE or ITX and identify the STIG compliance gaps and NIPR/SIPR boundary vulnerabilities before the evaluators do.
• 05Brief the battalion or regimental commander and the BSgtMaj on communications section morale, retention, gear readiness, and the second-order effects of policy decisions they cannot see from the conference room.
• 06Run a Red Cross or casualty notification with the dignity the family and the formation require — you are the face they remember.

• —MCDP 1 — Warfighting; MCDP 1-3 — Tactics (you teach these to the next generation of network Marines; you do not consume them).
• —MCO 1610.7 — Performance Evaluation System (you are the rater or reviewing officer on the FitReps that determine the next network GySgt and 1stSgt slates).
• —MCO 1400.32 — Marine Corps Promotion Manual (1stSgt / SgtMaj / MSgt / MGySgt board mechanics).
• —MCO 1900.16 — Marine Corps Retirement / Separation (you are the resource the formation comes to for transition questions).
• —DoDD 8500.01 — Cybersecurity; DISA STIGs (you hold the account that every IG and MARFORCYBER inspection validates against).
• —The Commandant's Reading List and current Planning Guidance — you are expected to consume strategic doctrine and translate it down to the network technicians.

• —SNCO Academy Senior Course graduate; Sergeants Major Course (Marine Corps University, Camp Geiger NC) before competing for command SgtMaj slate.
• —Company UCMJ rate, retention rate, and SAPR/EO climate index in the top tier of the battalion — the BSgtMaj reports up against every peer 1stSgt.
• —HBSS and ACAS compliance for the company at the ISSM-set threshold through every inspection during your tenure.
• —Zero senior-enlisted-level integrity incidents — financial, fraternization, OPSEC, cyber. One ends the career permanently at this rank and the Corps does not relitigate.
• —Post-service transition plan running 24 to 36 months out — VA disability claim filed pre-EAS, SkillBridge slot identified, retirement not walked into cold.

• —Going public with disagreement with the CO. You take the disagreement in his office with the door closed; you walk out aligned, every time.
• —Confusing seniority with leverage. The Corps keeps senior enlisted who serve the formation — not the ones who run their own program off the company commander's back.
• —Stopping personal PT because you are too senior. Marines stop respecting the chevrons when the body stops carrying them, and the 1st-Class PFT is still the bar.
• —Letting a GySgt run a bad HBSS compliance posture because he is your guy. The ISSM finds it, the regimental SgtMaj finds it, and the next slate is read without your name on it.
• —Confusing the warm-up to retirement with the job. Until you walk out of the formation for the last time, the formation is your job — the network Marines are still watching how you carry it.

The good 1stSgt / SgtMaj 0631 is the senior Marine every network Marine in the formation knows by face and reputation. He is the reason the re-enlistment line forms after a hard deployment with 12-hour network watch rotations and a MARFORCYBER inspection in the middle. The CO trusts him with the worst news at 0200; the Marines trust him to fight for the school slots, the gear upgrades, and the career decisions before walking away from what he cannot win. The good MGySgt is the Marine HQMC calls when the 0631 T&R program needs rewriting — and the GySgts in the regiment quote him at section training without realizing they are doing it.